| Age | Commit message (Collapse) | Author |
|---|
|
o read global SSL configuration file
o add GUC "ssl_ciphers" to control allowed ciphers
o add libpq environment variable PGSSLKEY to control SSL hardware keys
Victor B. Wagner
|
|
startup and bgwriter processes), and the -y flag. It's not used anywhere.
|
|
>
> o Use LC_TIME for localized weekday/month names, rather than
> LC_MESSAGES
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg00390.php
|
|
had never touched the subject before.
|
|
|
|
copied-and-pasted text in a more useful location.
|
|
> * Clean up casting in /contrib/isn
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg00245.php
>
|
|
> * Improve logging of prepared statements recovered during startup
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php
>
|
|
* Allow SQL-language functions to return results from RETURNING queries
>
> http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php
>
|
|
equality checks it applies, instead of a random dependence on whatever
operators might be named "=". The equality operators will now be selected
from the opfamily of the unique index that the FK constraint depends on to
enforce uniqueness of the referenced columns; therefore they are certain to be
consistent with that index's notion of equality. Among other things this
should fix the problem noted awhile back that pg_dump may fail for foreign-key
constraints on user-defined types when the required operators aren't in the
search path. This also means that the former warning condition about "foreign
key constraint will require costly sequential scans" is gone: if the
comparison condition isn't indexable then we'll reject the constraint
entirely. All per past discussions.
Along the way, make the RI triggers look into pg_constraint for their
information, instead of using pg_trigger.tgargs; and get rid of the always
error-prone fixed-size string buffers in ri_triggers.c in favor of building up
the RI queries in StringInfo buffers.
initdb forced due to columns added to pg_constraint and pg_trigger.
|
|
>
> http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php
>
|
|
* Update Bonjour to work with newer cross-platform SDK
> http://archives.postgresql.org/pgsql-patches/2006-10/msg00048.php
|
|
> * Improve failure message when DROP DATABASE is used on a database that
> has prepared transactions
|
|
* Update Bonjour to work with newer cross-platform SDK
>
> http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php
>
|
|
> * Update our code to handle 64-bit timezone files to match the zic
> source code, which now uses them
|
|
|
|
the RHS of the assignment expands to a reference to the LHS.
|
|
|
|
|
|
|
|
<
> http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php
|
|
< * Merge xmin/xmax/cmin/cmax back into three header fields
<
< Before subtransactions, there used to be only three fields needed to
< store these four values. This was possible because only the current
< transaction looks at the cmin/cmax values. If the current transaction
< created and expired the row the fields stored where xmin (same as
< xmax), cmin, cmax, and if the transaction was expiring a row from a
< another transaction, the fields stored were xmin (cmin was not
< needed), xmax, and cmax. Such a system worked because a transaction
< could only see rows from another completed transaction. However,
< subtransactions can see rows from outer transactions, and once the
< subtransaction completes, the outer transaction continues, requiring
< the storage of all four fields. With subtransactions, an outer
< transaction can create a row, a subtransaction expire it, and when the
< subtransaction completes, the outer transaction still has to have
< proper visibility of the row's cmin, for example, for cursors.
<
< One possible solution is to create a phantom cid which represents a
< cmin/cmax pair and is stored in local memory. Another idea is to
< store both cmin and cmax only in local memory.
<
> * -Merge xmin/xmax/cmin/cmax back into three header fields
|
|
< * Consider placing all sequences in a single table
> * Consider placing all sequences in a single table, or create a system
> view
|
|
< * Consider placing all sequences in a single table, now that system
< tables are full transactional
> * Consider placing all sequences in a single table
|
|
> * Consider placing all sequences in a single table, now that system
> tables are full transactional
|
|
* Add support for SQL-standard GENERATED/IDENTITY columns
> http://archives.postgresql.org/pgsql-hackers/2006-08/msg00038.php
|
|
ach backend to re-load all shared_preload_libraries.
Korry Douglas
|
|
Teodor Sigaev
|
|
version.
Backpatch to 8.2.X.
|
|
Backpatch to 8.2.X.
|
|
already collected in the current transaction; this allows plpgsql functions to
watch for stats updates even though they are confined to a single transaction.
Use this instead of the previous kluge involving pg_stat_file() to wait for
the stats collector to update in the stats regression test. Internally,
decouple storage of stats snapshots from transaction boundaries; they'll
now stick around until someone calls pgstat_clear_snapshot --- which xact.c
still does at transaction end, to maintain the previous behavior. This makes
the logic a lot cleaner, at the price of a couple dozen cycles per transaction
exit.
|
|
|
|
|
|
|
|
|
|
<P>USA saving time changes are included in PostgreSQL release 8.0.[4+],
and all later major releases, e.g. 8.1. Canada and Western Australia
changes are included in 8.0.[10+], 8.1.[6+], and all later major
releases. PostgreSQL releases prior to 8.0 use the operating system's
timezone database for daylight saving information.</P>
|
|
* -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h
* Consider making NAMEDATALEN more configurable in future releases
|
|
used to be part of libpq's exported interface many releases ago, but now
it's no longer necessary to make it accessible to clients.
|
|
|
|
markup's broken. So just remove it...
|
|
|
|
> o Add a \set variable to control whether \s displays line numbers
> Another option is to add \# which lists line numbers, and
> allows command execution.
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
|
|
< o Add \# to list command history like \s, but with line numbers
> o Add \# to list and execute command history
|
|
>
> * Allow custom variable classes that can restrict who can set the values
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php
>
|
|
|
|
Backpatch to 8.2.X.
|
|
* Allow sequential scans to take advantage of other concurrent
sequential scans, also called "Synchronised Scanning"
|
|
>
> o Add \# to list command history like \s, but with line numbers
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
>
|
|
* Allow sequential scans to take advantage of other concurrent
sequential scans, also called "Synchronised Scanning"
> http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php
|
|
gmake -C src/bin install
does install a few server-only binaries.
|
