https://github.com/postgres/postgres

sort by:
Revision Author Date Message Commit Date
4fa7615 Rename encryption section. 09 May 2005, 17:26:55 UTC
00283f4 Backpatch FAQ's to 8.0.X for release. 09 May 2005, 17:24:04 UTC
014fce9 Backpatch encryption doc section to 8.0.X. 09 May 2005, 17:14:47 UTC
8fae368 Update release notes for upcoming re-releases. 09 May 2005, 00:10:06 UTC
16379e3 Update release checklist to reflect that HISTORY and INSTALL don't need to be created by hand anymore. 08 May 2005, 23:34:23 UTC
d6e30b0 Repair very-low-probability race condition between relation extension 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. 07 May 2005, 21:32:53 UTC
aba1f93 Adjust time qual checking code so that we always check TransactionIdIsInProgress 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. 07 May 2005, 21:22:36 UTC
17eb867 Stamp release 8.0.3. 05 May 2005, 20:07:36 UTC
266a897 Make standalone backends ignore pg_database.datallowconn, so that there is a way to recover from disabling connections to all databases at once. 05 May 2005, 19:53:37 UTC
fbacd78 Add WSACleanup() for Win32 socket cleanup. Jason Erickson 05 May 2005, 16:36:20 UTC
b22bbd6 Use postmaster_is_alive() check in pg_ctl restart as well as pg_ctl status, so that restart doesn't fail when old postmaster died unbetimes. 04 May 2005, 22:35:22 UTC
32083d2 Spell DELIMITER correctly, per Seamus Dean. 04 May 2005, 14:25:30 UTC
4afab96 Alter the signature for encoding conversion functions to declare the 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. 03 May 2005, 19:18:16 UTC
298e077 Change tsearch2 to not use the unsafe practice of creating functions 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 :-( 03 May 2005, 16:51:22 UTC
d0069f5 Fix a whitespace problem. From Alvaro Herrera. 03 May 2005, 06:28:24 UTC
323fe83 Backport fix for correct quoting in CREATE DOMAIN example. Per Robert Treat. 02 May 2005, 01:56:16 UTC
50433d6 Make record_out and record_send extract type information from the passed 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. 30 April 2005, 20:04:46 UTC
757956e GCC 4.0 includes a new warning option, -Wformat-literal, that emits 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. 30 April 2005, 08:19:44 UTC
7ce0179 This patch fixes a bug in the error message emitted by pg_restore on an incorrect -F argument: write_msg() expects its first parameter to be a "module name", not the format string. 30 April 2005, 08:00:14 UTC
f22b3b2 Improve cleanup from win32 client-only build. 29 April 2005, 14:07:34 UTC
5f9d19c Backpatch BCC compile changes to 8.0.X for psql. 29 April 2005, 13:42:24 UTC
95cb42b Fix Borland makefile for libpq and improve it for psql. Reorder MSC makefile to be more consistent and easier to maintain. 29 April 2005, 04:21:39 UTC
115119e Wording improvement. 27 April 2005, 20:11:11 UTC
5e46908 Update PAM documentation, per Alvaro. 27 April 2005, 20:09:58 UTC
46edb8e workaround for bug in utils/date.h (timetz) 27 April 2005, 13:01:27 UTC
575d7d0 Mention that PAM requires the user already exist in the database, per Dick Davies. 26 April 2005, 03:01:22 UTC
73c195c Fix btree_gist to handle timetz zone correctly per recent changes. 25 April 2005, 16:58:18 UTC
582dcae Repair two TIME WITH TIME ZONE bugs found by Dennis Vshivkov. Comparison 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). 23 April 2005, 22:53:26 UTC
58d0214 int_aggregate's int_enum() doesn't work correctly with arrays that aren't 1-D, so give an error message instead of failing. Per report from Ron Mayer. 23 April 2005, 05:38:43 UTC
8e4b89c Backpatch of LIMIT / FOR UPDATE behavior, but keep pre-7.3 mention in 8.0.X. 22 April 2005, 15:53:27 UTC
ddae2b6 Clarify that only crypt can't use md5 pg_shadow passwords. 22 April 2005, 04:19:02 UTC
4f6d275 Clarify use of MD5 authentication and pg_shadow encryption. 21 April 2005, 22:19:27 UTC
1275ad5 Make pg_ctl status do a kill() test to verify that the PID found in postmaster.pid still represents a live postmaster. 20 April 2005, 23:10:22 UTC
eecc925 Don't try to run clauseless index scans on index types that don't support it. Per report from Marinos Yannikos. 20 April 2005, 21:48:12 UTC
25bd301 Fix mis-display of negative fractional seconds in interval values for --enable-integer-datetimes case. Per report from Oliver Siegmar. 20 April 2005, 17:14:58 UTC
cc5b676 Add comment about permissions on pg_ts* tables 19 April 2005, 13:58:11 UTC
0a2400e Update PITR wording, per Simon. 19 April 2005, 01:40:02 UTC
92645c4 pg_dumpall should enforce the server version check for itself, rather than simply passing it down to pg_dump. Else, version-related failures in pg_dumpall itself generate unhelpful error messages. 18 April 2005, 23:48:01 UTC
1186365 record_in and record_recv must be careful to return a separately 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. 18 April 2005, 17:11:15 UTC
fef57bd Update PITR mention of which WAL files are needed. 18 April 2005, 01:29:08 UTC
2bf3ab9 Clarify name of file to be checked for PITR expiring. 17 April 2005, 03:05:27 UTC
96d61bc Fix comment typo. 15 April 2005, 22:49:45 UTC
beb9e2e Revert addition of poorly-thought-out DUMP TIMESTAMP archive entry, 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. 15 April 2005, 16:40:59 UTC
69cb5ac Make equalTupleDescs() compare attlen/attbyval/attalign rather than 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. 14 April 2005, 22:35:12 UTC
59974b0 Don't try to constant-fold functions returning RECORD, since the optimizer 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. 14 April 2005, 21:44:22 UTC
c61d1c9 Added patch by Philip Yarra <philip.yarra@internode.on.net> for a bug in thread support. 14 April 2005, 10:09:20 UTC
fa57fd1 Fix interaction between materializing holdable cursors and firing deferred triggers: either one can create more work for the other, so we have to loop till it's all gone. Per example from andrew@supernews. Add a regression test to help spot trouble in this area in future. 11 April 2005, 19:51:32 UTC
add2c3f PersistHoldablePortal must establish the correct value for ActiveSnapshot while completing execution of the cursor's query. Otherwise we get wrong answers or even crashes from non-volatile functions called by the query. Per report from andrew@supernews. 11 April 2005, 15:59:47 UTC
88b229d Make constant-folding produce sane output for COALESCE(NULL,NULL), that is a plain NULL and not a COALESCE with no inputs. Fixes crash reported by Michael Williamson. 10 April 2005, 20:57:45 UTC
c8814f4 SQL functions returning pass-by-reference types were copying the results into the wrong memory context, resulting in a query-lifespan memory leak. Bug is new in 8.0, I believe. Per report from Rae Stiening. 10 April 2005, 18:04:31 UTC
7dbded2 Stamp 8.0.2. 07 April 2005, 19:43:06 UTC
9b84381 Update and copy-edit release notes for 8.0.2. 07 April 2005, 19:04:19 UTC
b93529f In cost_mergejoin, the early-exit effect should not apply to the outer side of an outer join. Per andrew@supernews. 04 April 2005, 01:43:23 UTC
9e57970 Put back code mistakenly removed from copy of postmaster's daemonize routine, namely forcing stdin/stdout/stderr to point to /dev/null. Per Karl Denninger. 03 April 2005, 00:02:03 UTC
774cdb9 Translation updates 02 April 2005, 18:45:19 UTC
5b7ef0d Translation updates 02 April 2005, 15:54:57 UTC
9c4b347 Fix release not typo. 02 April 2005, 03:43:08 UTC
6176eb5 Update release notes for 8.0.2. 02 April 2005, 02:42:59 UTC
f0aa94f Second try at making examine_variable and friends behave sanely in cases with binary-compatible relabeling. My first try was implicitly assuming that all operators scalarineqsel is used for have binary- compatible datatypes on both sides ... which is very wrong of course. Per report from Michael Fuhr. 01 April 2005, 20:32:09 UTC
558dace Backpatch FAQ's to 8.0.X. 01 April 2005, 16:42:59 UTC
cc20233 Fix wrong week returnded by date_trunc('week') for early dates in January --- would return wrong year for 2005-01-01 and 2006-01-01. per report from Robert Creager. Backpatch to 8.0.X. 01 April 2005, 14:25:39 UTC
ab6853e Flush any remaining statistics counts out to the collector at process exit. Without this, operations triggered during backend exit (such as temp table deletions) won't be counted ... which given heavy usage of temp tables can lead to pg_autovacuum falling way behind on the need to vacuum pg_class and pg_attribute. Per reports from Steve Crawford and others. 31 March 2005, 23:21:09 UTC
5530877 Translation updates 31 March 2005, 18:14:25 UTC
da2010f Fix various comparing functions 31 March 2005, 15:10:48 UTC
01ebb55 Document that the "-P" option to pg_autovacuum is insecure on many platforms, and suggest using ~/.pgpass instead. 30 March 2005, 05:06:32 UTC
90ce397 Fix a pair of related issues with estimation of inequalities that involve binary-compatible relabeling of one or both operands. examine_variable should avoid stripping RelabelType from non-variable expressions, so that they will continue to have the correct type; and convert_to_scalar should just use that type and ignore the other input type. This isn't perfect but it beats failing entirely. Per example from Michael Fuhr. 26 March 2005, 20:55:58 UTC
d4f7278 Make additional stamps for 8.0.2. 26 March 2005, 05:05:23 UTC
507fc3c Tag for 8.0.2beta1 26 March 2005, 03:46:33 UTC
9b31b4a Add Windows-specific variant comparison file. 26 March 2005, 03:38:11 UTC
cc31f7e Add another ORDER BY to rules test to eliminate platform-specific output ordering. 26 March 2005, 02:14:54 UTC
209bc96 Prevent to_char(interval) from dumping core on month-related formats when a zero-month interval is given. Per discussion with Karel. Also, some desultory const-labeling of constant tables. More could be done along that line. 26 March 2005, 00:41:45 UTC
869825c Remove lazy_update_relstats; go back to having VACUUM just record the actual number of unremoved tuples as pg_class.reltuples. The idea of trying to estimate a steady state condition still seems attractive, but this particular implementation crashed and burned ... 25 March 2005, 22:51:42 UTC
7751c06 Have libpgport link before libpq so that PG client applications are more immunte to changes in libpq's usage of pgport between major versions. Backpatch to 8.0.X. 25 March 2005, 18:18:41 UTC
42a00ef Fix two bugs in change_owner_recurse_to_sequences: it was grabbing an overly strong lock on pg_depend, and it wasn't closing the rel when done. The latter bug was masked by the ResourceOwner code, which is something that should be changed. 25 March 2005, 18:04:47 UTC
ae7c18d Update and copy-edit description of privileges. 25 March 2005, 16:39:03 UTC
f87592f Add missing min/max parameters to DefineCustomIntVariable() and DefineCustomRealVariable(). Thomas Hallgren 25 March 2005, 16:17:39 UTC
88f07b1 Fix to_date to behave reasonably when CC and YY fields are both used. Karel Zak 25 March 2005, 16:08:50 UTC
8416036 Kerberos fixes from Magnus Hagander --- in theory Kerberos 5 auth should work on Windows now. Also, rename set_noblock to pg_set_noblock; since it is included in libpq, the former name polluted application namespace. 25 March 2005, 00:35:20 UTC
cb2a2fd Revert ill-conceived change of libpq linkage --- breaks ecpg. 24 March 2005, 23:54:01 UTC
e1fc339 array_map can't use the fn_extra field of the provided fcinfo struct as its private storage, because that belongs to the function that it is supposed to call. Per report from Ezequiel Tolnay. 24 March 2005, 21:50:52 UTC
d5595f9 Force PG client applications to link to non-shared libpgport before linking to libpq. This insulates applications from changes in libpq's usage of libpgport functions. Backpatched to 8.0.X. 24 March 2005, 19:33:40 UTC
b741e9d Tweak planner to use a minimum size estimate of 10 pages for a never-yet-vacuumed relation. This restores the pre-8.0 behavior of avoiding seqscans during initial data loading, while still allowing reasonable optimization after a table has been vacuumed. Several regression test cases revert to 7.4-like behavior, which is probably a good sign. Per gripes from Keith Browne and others. 24 March 2005, 19:15:11 UTC
dd0702a Fix python regression testing script to bail out early if language creation fails ... no point in running the tests. 24 March 2005, 17:23:39 UTC
35411a8 Adjust plpython to convert \r\n and \r to \n in Python scripts, per recent discussion concluding that this is the Right Thing. Add regression test check for this behavior. Michael Fuhr 24 March 2005, 17:22:44 UTC
291cd95 Change Win32 O_SYNC method to O_DSYNC because that is what the method currently does. This is now the default Win32 wal sync method because we perfer o_datasync to fsync. Also, change Win32 fsync to a new wal sync method called fsync_writethrough because that is the behavior of _commit, which is what is used for fsync on Win32. Backpatch to 8.0.X. 24 March 2005, 04:37:07 UTC
3781b72 Add missing error checking in readdir() loops. 24 March 2005, 02:11:33 UTC
63b0d7b Add note about risks involved in replaying CREATE TABLESPACE commands from WAL. A couple other grammatical improvements too. 23 March 2005, 19:39:06 UTC
a4500f3 Previous "64-bit fix" for intagg didn't actually work. This is already fixed properly in CVS tip, but we need a band-aid for back branches. Per report from Ron Mayer. 23 March 2005, 19:06:54 UTC
5869e88 WAL must log CREATE and DROP DATABASE operations *without* using any explicit paths, so that the log can be replayed in a data directory with a different absolute path than the original had. To avoid forcing initdb in the 8.0 branch, continue to accept the old WAL log record types; they will never again be generated however, and the code can be dropped after the next forced initdb. Per report from Oleg Bartunov. We still need to think about what it really means to WAL-log CREATE TABLESPACE commands: we more or less have to put the absolute path into those, but how to replay in a different context?? 23 March 2005, 00:04:25 UTC
1cef5be Fix quote_ident to use quote_identifier rather than its own, not quite up-to-speed logic; in particular this will cause it to quote names that match keywords. Remove unnecessary multibyte cruft from quote_literal (all backend-internal encodings are 8-bit-safe). 21 March 2005, 16:29:31 UTC
8ae13aa Put 'dump complete' message in the right place, so it comes out where it's supposed to when --file option is used. 18 March 2005, 17:33:03 UTC
817bc02 Need to reset local buffer pin counts, not only shared buffer pins, before we attempt any file deletions in ShutdownPostgres. Per Tatsuo. 18 March 2005, 16:16:20 UTC
fc80f5f Added patch by Christof Petig <christof@petig-baender.de> to work around gcc bug on powerpc and amd64. 18 March 2005, 10:01:14 UTC
b030725 Need to release buffer pins before attempting to drop files during backend exit. Per report from Bruce. 18 March 2005, 05:24:24 UTC
bcfe508 Treat EPERM as a non-error case when checking to see if old postmaster is still alive. This improves our odds of not getting fooled by an unrelated process when checking a stale lock file. Other checks already in place, plus one newly added in checkDataDir(), ensure that we cannot attempt to usurp the place of a postmaster belonging to a different userid, so there is no need to error out. Add comments indicating the importance of these other checks. 18 March 2005, 03:49:19 UTC
7911e3a Backpatch to 8.0.X, already in HEAD: Allow Win32 to support the O_SYNC open flag as an wal_sync_method method. 17 March 2005, 17:28:59 UTC
89ea098 Add missing include for new lc_ctype_is_c() function. Per Neil. 16 March 2005, 01:49:20 UTC
fb2c2d8 Prevent locale-aware handling of upper, lower, and initcap when the locale is C. Backpatch to 8.0.X because some operating systems were throwing errors for such operations, rather than ignoring the locale when it was C. 16 March 2005, 00:03:02 UTC
f38cb72 Increment all major version numbers in 8.0.X to force recompile of client aplications so 7.4.X releases can be installed on the same machine as 8.0.X. 13 March 2005, 22:04:45 UTC
b3dbaab Fix ALTER DATABASE RENAME to allow the operation if user is a superuser who for some reason isn't marked usecreatedb. Per report from Alexander Pravking. Also fix sloppy coding in have_createdb_privilege(). 12 March 2005, 21:12:05 UTC
back to top