aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Document that bcc compiles now need the -N flag, backpatch to 8.0.X.Bruce Momjian2005-05-11
|
* Update Chinese FAQ, per Magnus.Bruce Momjian2005-05-11
|
* Backpatch mention that not all functions are listed, with spelling fix.Bruce Momjian2005-05-11
|
* Add mention that not all functions are listed.Bruce Momjian2005-05-11
| | | | Update Chinese FAQ for HTML.
* Backpatch new Chinese FAQ to 8.0.X.Bruce Momjian2005-05-11
|
* Rename encryption section.REL8_0_3Bruce Momjian2005-05-09
|
* Backpatch FAQ's to 8.0.X for release.Bruce Momjian2005-05-09
|
* Backpatch encryption doc section to 8.0.X.Bruce Momjian2005-05-09
|
* Update release notes for upcoming re-releases.Tom Lane2005-05-09
|
* Update release checklist to reflect that HISTORY and INSTALL don'tTom Lane2005-05-08
| | | | need to be created by hand anymore.
* Repair very-low-probability race condition between relation extensionTom Lane2005-05-07
| | | | | | | | and VACUUM: in the interval between adding a new page to the relation and formatting it, it was possible for VACUUM to come along and decide it should format the page too. Though not harmful in itself, this would cause data loss if a third transaction were able to insert tuples into the vacuumed page before the original extender got control back.
* Adjust time qual checking code so that we always check TransactionIdIsInProgressTom Lane2005-05-07
| | | | | | | before we check commit/abort status. Formerly this was done in some paths but not all, with the result that a transaction might be considered committed for some purposes before it became committed for others. Per example found by Jan Wieck.
* Stamp release 8.0.3.Tom Lane2005-05-05
|
* Make standalone backends ignore pg_database.datallowconn, so that thereTom Lane2005-05-05
| | | | is a way to recover from disabling connections to all databases at once.
* Add WSACleanup() for Win32 socket cleanup.Bruce Momjian2005-05-05
| | | | Jason Erickson
* Use postmaster_is_alive() check in pg_ctl restart as well as pg_ctl status,Tom Lane2005-05-04
| | | | so that restart doesn't fail when old postmaster died unbetimes.
* Spell DELIMITER correctly, per Seamus Dean.Tom Lane2005-05-04
|
* Alter the signature for encoding conversion functions to declare theTom Lane2005-05-03
| | | | | | output area as INTERNAL not CSTRING. This is to prevent people from calling the functions by hand. This is a permanent solution for the back branches but I hope it is just a stopgap for HEAD.
* Change tsearch2 to not use the unsafe practice of creating functionsTom Lane2005-05-03
| | | | | | | | that return INTERNAL without also having INTERNAL arguments. Since the functions in question aren't meant to be called by hand anyway, I just redeclared them to take 'internal' instead of 'text'. Also add code to ProcedureCreate() to enforce the restriction, as I should have done to start with :-(
* Fix a whitespace problem. From Alvaro Herrera.Dennis Bjorklund2005-05-03
|
* Backport fix for correct quoting in CREATE DOMAIN example. Per RobertNeil Conway2005-05-02
| | | | Treat.
* Make record_out and record_send extract type information from the passedTom Lane2005-04-30
| | | | | | | record object itself, rather than relying on a second OID argument to be correct. This patch just changes the function behavior and not the catalogs, so it's OK to back-patch to 8.0. Will remove the now-redundant second argument in pg_proc in a separate patch in HEAD only.
* GCC 4.0 includes a new warning option, -Wformat-literal, that emitsNeil Conway2005-04-30
| | | | | | | | | | | | | | | a warning when a variable is used as a format string for printf() and similar functions (if the variable is derived from untrusted data, it could include unexpected formatting sequences). This emits too many warnings to be enabled by default, but it does flag a few dubious constructs in the Postgres tree. This patch fixes up the obvious variants: functions that are passed a variable format string but no additional arguments. Most of these are harmless (e.g. the ruleutils stuff), but there is at least one actual bug here: if you create a trigger named "%sfoo", pg_dump will read uninitialized memory and fail to dump the trigger correctly.
* This patch fixes a bug in the error message emitted by pg_restore on anNeil Conway2005-04-30
| | | | | incorrect -F argument: write_msg() expects its first parameter to be a "module name", not the format string.
* Improve cleanup from win32 client-only build.Bruce Momjian2005-04-29
|
* Backpatch BCC compile changes to 8.0.X for psql.Bruce Momjian2005-04-29
|
* Fix Borland makefile for libpq and improve it for psql.Bruce Momjian2005-04-29
| | | | Reorder MSC makefile to be more consistent and easier to maintain.
* Wording improvement.Bruce Momjian2005-04-27
|
* Update PAM documentation, per Alvaro.Bruce Momjian2005-04-27
|
* workaround for bug in utils/date.h (timetz)Teodor Sigaev2005-04-27
|
* Mention that PAM requires the user already exist in the database, perBruce Momjian2005-04-26
| | | | Dick Davies.
* Fix btree_gist to handle timetz zone correctly per recent changes.Tom Lane2005-04-25
|
* Repair two TIME WITH TIME ZONE bugs found by Dennis Vshivkov. ComparisonTom Lane2005-04-23
| | | | | | | of timetz values misbehaved in --enable-integer-datetime cases, and EXTRACT(EPOCH) subtracted the zone instead of adding it in all cases. Backpatch to all supported releases (except --enable-integer-datetime code does not exist in 7.2).
* int_aggregate's int_enum() doesn't work correctly with arrays thatTom Lane2005-04-23
| | | | | aren't 1-D, so give an error message instead of failing. Per report from Ron Mayer.
* Backpatch of LIMIT / FOR UPDATE behavior, but keep pre-7.3 mention in 8.0.X.Bruce Momjian2005-04-22
|
* Clarify that only crypt can't use md5 pg_shadow passwords.Bruce Momjian2005-04-22
|
* Clarify use of MD5 authentication and pg_shadow encryption.Bruce Momjian2005-04-21
|
* Make pg_ctl status do a kill() test to verify that the PID found inTom Lane2005-04-20
| | | | postmaster.pid still represents a live postmaster.
* Don't try to run clauseless index scans on index types that don't supportTom Lane2005-04-20
| | | | it. Per report from Marinos Yannikos.
* Fix mis-display of negative fractional seconds in interval values forTom Lane2005-04-20
| | | | --enable-integer-datetimes case. Per report from Oliver Siegmar.
* Add comment about permissions on pg_ts* tablesTeodor Sigaev2005-04-19
|
* Update PITR wording, per Simon.Bruce Momjian2005-04-19
|
* pg_dumpall should enforce the server version check for itself, ratherTom Lane2005-04-18
| | | | | than simply passing it down to pg_dump. Else, version-related failures in pg_dumpall itself generate unhelpful error messages.
* record_in and record_recv must be careful to return a separatelyTom Lane2005-04-18
| | | | | pfree'able result, since some callers expect to be able to pfree the result of a pass-by-reference function. Per report from Chris Trawick.
* Update PITR mention of which WAL files are needed.Bruce Momjian2005-04-18
|
* Clarify name of file to be checked for PITR expiring.Bruce Momjian2005-04-17
|
* Fix comment typo.Bruce Momjian2005-04-15
|
* Revert addition of poorly-thought-out DUMP TIMESTAMP archive entry,Tom Lane2005-04-15
| | | | | | | | which induced bug #1597 in addition to having several other misbehaviors (like labeling the dump with a completion time having nothing to do with reality). Instead just print out the desired strings where RestoreArchive was already emitting the 'PostgreSQL database dump' and 'PostgreSQL database dump complete' strings.
* Make equalTupleDescs() compare attlen/attbyval/attalign rather thanTom Lane2005-04-14
| | | | | | | | | | assuming comparison of atttypid is sufficient. In a dropped column atttypid will be 0, and we'd better check the physical-storage data to make sure the tupdescs are physically compatible. I do not believe there is a real risk before 8.0, since before that we only used this routine to compare successive states of the tupdesc for a particular relation. But 8.0's typcache.c might be comparing arbitrary tupdescs so we'd better play it safer.
* Don't try to constant-fold functions returning RECORD, since the optimizerTom Lane2005-04-14
| | | | | isn't presently set up to pass them an expected tuple descriptor. Bug has been there since 7.3 but was just recently reported by Thomas Hallgren.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-07 20:55:39 +0000