| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| |
|
|
|
|
|
|
|
| |
< * Prevent libpq's PQfnumber() from lowercasing the column name?
> * Prevent libpq's PQfnumber() from lowercasing the column name
>
> One idea is to lowercase all identifiers except those that are
> surrounded by quotes.
>
|
| |
|
|
| |
> o Add options like pg_restore -l and -L to pg_dump
|
| |
|
|
|
|
|
| |
> o Allow selection of individual object(s) of all types, not just
> tables
> o In a selective dump, allow dumping of an object and all its
> dependencies
|
| | |
|
| |
|
|
|
|
|
|
| |
emit when given the --clean option, in favor of individual DROP ROLE
commands. The old technique could not possibly work in 8.1, and was
never a very good idea anyway IMHO. The DROP ROLE approach has the
defect that the DROPs will fail for roles that own objects or have
privileges, but perhaps we can improve that later.
|
| | |
|
| |
|
|
|
|
|
|
| |
< * Consider compressing indexes by storing key prefix values shared by
> * Consider compressing indexes by storing key values duplicated in
735a736,737
>
> This is difficult because it requires datatype-specific knowledge.
|
| |
|
|
|
|
| |
<
> * Consider compressing indexes by storing key prefix values shared by
> several rows as a single index entry
|
| | |
|
| |
|
|
|
|
|
| |
generated by bitmap index scans. Along the way, simplify and speed up
the code for counting sequential and index scans; it was both confusing
and inefficient to be taking care of that in the per-tuple loops, IMHO.
initdb forced because of internal changes in pg_stat view definitions.
|
| | |
|
| |
|
|
| |
Jun Kuwamura
|
| | |
|
| |
|
|
| |
renamed to --log-file for clarity.
|
| |
|
|
| |
where it should prohibit COPY FROM. Found by Alon Goldshuv.
|
| |
|
|
| |
sort operations. Per recent discussion. Simon Riggs and Tom Lane.
|
| |
|
|
| |
Update release dates for pending back-branch releases.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
early binding for nextval() calls in default clauses.
|
| |
|
|
| |
< * -Have sequence dependency track use of DEFAULT sequences
|
| |
|
|
|
|
| |
< * Have sequence dependency track use of DEFAULT sequences,
< seqname.nextval?
> * -Have sequence dependency track use of DEFAULT sequences
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
argument as a 'regclass' value instead of a text string. The frontend
conversion of text string to pg_class OID is now encapsulated as an
implicitly-invocable coercion from text to regclass. This provides
backwards compatibility to the old behavior when the sequence argument
is explicitly typed as 'text'. When the argument is just an unadorned
literal string, it will be taken as 'regclass', which means that the
stored representation will be an OID. This solves longstanding problems
with renaming sequences that are referenced in default expressions, as
well as new-in-8.1 problems with renaming such sequences' schemas or
moving them to another schema. All per recent discussion.
Along the way, fix some rather serious problems in dbmirror's support
for mirroring sequence operations (int4 vs int8 confusion for instance).
|
| | |
|
| |
|
|
| |
SQL option spelling.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
subsystem reliability.
|
| | |
|
| |
|
|
| |
Victor Vislobokov
|
| | |
|
| |
|
|
|
| |
< * +Add options to pg_config to show the share_dir, sysconfdir,
< pkgincludedir, and localedir
|
| |
|
|
|
|
|
| |
relocated after installation. We can't trust the installation paths
inserted into Makefile.global by configure, so instead we must get the
paths from pg_config. This requires extending pg_config to support all
the separately-configurable path names, but that was on TODO anyway.
|
| | |
|
| |
|
|
|
| |
> o Improve signal handling,
> http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php
|
| |
|
|
|
| |
< * Add options to pg_config to show the share_dir, sysconfdir,
> * +Add options to pg_config to show the share_dir, sysconfdir,
|
| | |
|
| |
|
|
|
| |
< * Allow protocol-level EXECUTE that is actually a fetch to appear
< in the logs as a fetch rather than another execute
|
| |
|
|
|
|
| |
> * Allow protocol-level BIND parameter values to be logged
> * Allow protocol-level EXECUTE that is actually a fetch to appear
> in the logs as a fetch rather than another execute
|
| | |
|
| |
|
|
| |
DLL compiles to not match the application.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
compatibility issue.
|
