| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
Martijn van Oosterhout
|
|
|
|
|
|
| |
CPPFLAGS, CFLAGS, CFLAGS_SL, LDFLAGS, LDFLAGS_SL, and LIBS. Change it
so that invoking pg_config with no arguments reports all available
information, rather than just giving an error message. Per discussion.
|
|
|
|
|
|
| |
< inheritance
< * Allow enable_constraint_exclusion to work for UPDATE and DELETE queries
> inheritance, and allow it to work for UPDATE and DELETE queries
|
|
|
|
| |
> * -Add C code on Unix to copy directories for use in creating new databases
|
| |
|
| |
|
|
|
|
| |
> * -Allow multiple blocks to be written to WAL with one write()
|
| |
|
|
|
|
| |
> o -Allow FOR UPDATE queries to do NOWAIT locks
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was not especially critical before, but it is now that we track
ownership dependencies --- the dependency for the rowtype *must* shift
to the new owner. Spotted by Bernd Helmle.
Also fix a problem introduced by recent change to allow non-superusers
to do ALTER OWNER in some cases: if the table had a toast table, ALTER
OWNER failed *even for superusers*, because the test being applied would
conclude that the new would-be owner had no create rights on pg_toast.
A side-effect of the fix is to disallow changing the ownership of indexes
or toast tables separately from their parent table, which seems a good
idea on the whole.
|
|
|
|
|
| |
< * Prevent inherited tables from expanding temporary subtables of other
> * -Prevent inherited tables from expanding temporary subtables of other
|
| |
|
|
|
|
|
| |
Original patch by Hans-Juergen Schoenig, revisions by Karel Zak
and Tom Lane.
|
| |
|
|
|
|
| |
editorialization.
|
|
|
|
| |
> * -Allow limits on per-db/role connections
|
|
|
|
|
|
|
|
|
|
|
|
| |
< o Allow objects to be moved to different schemas
> o -Allow objects to be moved to different schemas
Fix word wrap:
< * Allow GRANT/REVOKE permissions to be applied to all schema objects with one
< command
> o Allow GRANT/REVOKE permissions to be applied to all schema objects
> with one command
|
|
|
|
|
|
|
|
|
|
| |
< This would require a new global table that is dumped to flat file for
< use by the postmaster. We do a similar thing for pg_shadow currently.
> This would add a function to load the SQL table from
> pg_hba.conf, and one to writes its contents to the flat file.
> The table should have a line number that is a float so rows
> can be inserted between existing rows, e.g. row 2.5 goes
> between row 2 and row 3.
|
|
|
|
|
| |
This patch also includes preliminary update of pg_dumpall for roles.
Petr Jelinek, with review by Bruce Momjian and Tom Lane.
|
|
|
|
|
|
| |
< o Allow postgresql.conf file values to be changed via an SQL API
> o Allow postgresql.conf file values to be changed via an SQL
> API, perhaps using SET GLOBAL
|
|
|
|
|
|
| |
< * Allow server logs to be remotely read using SQL commands
151a151
> * Allow server logs to be remotely read and removed using SQL commands
|
| |
|
|
|
|
| |
place.
|
| |
|
| |
|
|
|
|
| |
Alvaro Herrera
|
|
|
|
|
|
| |
count.
Oliver Jowett
|
|
|
|
|
|
|
|
|
| |
tests for the new interval->day changes. I added tests for
justify_hours() and justify_days() to interval.sql, as they take
interval input and produce interval output. If there's a more
appropriate place for them, please let me know.
Michael Glaesemann
|
|
|
|
|
|
|
|
|
| |
<
> * Allow EXPLAIN to identify tables that were skipped because of
> enable_constraint_exclusion
> * Allow EXPLAIN output to be more easily processed by scripts
760a763
> * Allow enable_constraint_exclusion to work for UPDATE and DELETE queries
|
|
|
|
|
|
| |
<
> * Allow enable_constraint_exclusion to work for UNIONs like it does for
> inheritance
|
|
|
|
|
| |
> * Prevent inherited tables from expanding temporary subtables of other
> sessions
|
|
|
|
|
|
|
| |
> * Add system view to show free space map contents
884c885
< o Move into the backend code
> o -Move into the backend code
|
|
|
|
| |
> * Allow SELECT ... FOR UPDATE on inherited tables
|
|
|
|
|
| |
< * Add TRUNCATE permission
> * Add a separate TRUNCATE permission
|
|
|
|
|
|
|
|
| |
> * Add TRUNCATE permission
>
> Currently only the owner can TRUNCATE a table because triggers are not
> called, and the table is locked in exclusive mode.
>
|
|
|
|
| |
> * Add PQescapeIdentifier() to libpq
|
|
|
|
|
|
|
| |
>
> If CRC check fails during recovery, remember the page in case
> a later CRC for that page properly matches.
>
|
|
|
|
| |
Euler Taveira de Oliveira
|
|
|
|
|
|
|
|
|
|
|
|
| |
pg_tablespace_size
pg_database_size
pg_relation_size
pg_complete_relation_size
pg_size_pretty
Remove /contrib/dbsize.
Dave Page
|
|
|
|
|
|
| |
new commands which may make an SPI call fail.
Alvaro Herrera
|
|
|
|
|
|
|
| |
< * Consider use of open/fcntl(O_DIRECT) to minimize OS caching,
< especially for WAL writes
> * -Consider use of open/fcntl(O_DIRECT) to minimize OS caching,
> for WAL writes
|
| |
|
|
|
|
| |
be rewritten, but at least the reference pages are reasonably sane.
|
|
|
|
|
|
|
|
|
| |
doesn't automatically inherit the privileges of roles it is a member of;
for such a role, membership in another role can be exploited only by doing
explicit SET ROLE. The default inherit setting is TRUE, so by default
the behavior doesn't change, but creating a user with NOINHERIT gives closer
adherence to our current reading of SQL99. Documentation still lacking,
and I think the information schema needs another look.
|
|
|
|
|
|
|
| |
existing ones for object privileges. Update the information_schema for
roles --- pg_has_role() makes this a whole lot easier, removing the need
for most of the explicit joins with pg_user. The views should be a tad
faster now, too. Stephen Frost and Tom Lane.
|
|
|
|
| |
I'm still working on the has_role function and information_schema changes.
|
|
|
|
|
| |
> o Allow postgresql.conf file values to be changed via an SQL API
> o Allow the server to be stopped/restarted via an SQL API
|
|
|
|
|
|
| |
fails near DST transition days, so remove the advice about that testing
problem. Also improve the description of variant-comparison-file
selection.
|
|
|
|
|
| |
scans are candidates for exclusion; this should be fixed eventually.
Simon Riggs, with some help from Tom Lane.
|
|
|
|
|
|
|
|
|
|
| |
test=> select ('2005-07-20 00:00:00'::timestamp without time zone) at
time zone 'Europe/Paris';
timezone
------------------------
2005-07-19 22:00:00-04
Udpate documentation.
|