aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Explain privileges required for LOCK. Minor wordsmithing too.Tom Lane2002-01-18
|
* Point out that superusers bypass privilege checking. Minor wordsmithing.Tom Lane2002-01-18
|
* Fix misstatements added by Bruce.Tom Lane2002-01-16
|
* Add more comments to tqual.c for visibility functions.Bruce Momjian2002-01-16
|
* TOAST needs to do at least minimal time-qual checking in order not toTom Lane2002-01-16
| | | | | | | | | | | mess up after an aborted VACUUM FULL, per today's pghackers discussion. Add a suitable HeapTupleSatisfiesToast routine. Remove useless special- case test in HeapTupleSatisfiesVisibility macro for xmax = BootstrapTransactionId; perhaps that was needed at one time, but it's a waste of cycles now, not to mention actively wrong for SnapshotAny. Along the way, add some much-needed comments to tqual.c, and simplify toast_fetch_datum, which no longer needs to assume it may see chunks out-of-order.
* Fix init_irels to close the pg_internal.init file before returning.Tom Lane2002-01-16
| | | | | | This saves one open file descriptor per backend, and avoids an annoying NOTICE on Cygwin (which has trouble deleting open files). Bug appears to date back to original coding of init_irels, circa 1992.
* If we fail to rename pg_internal.init into place, delete the uselessTom Lane2002-01-15
| | | | | temporary file. This seems to be a known failure mode under Cygwin, so we might as well expend the extra line of code to be tidy.
* Add more sanity-checking to PageAddItem and PageIndexTupleDelete,Tom Lane2002-01-15
| | | | | | | to prevent spreading of corruption when page header pointers are bad. Merge PageZero into PageInit, since it was never used separately, and remove separate memset calls used at most other PageInit call points. Remove IndexPageCleanup, which wasn't used at all.
* Fix typo that caused equalTriggerDescs() to return false in cases whereTom Lane2002-01-15
| | | | | the two trigger sets were logically equal, but not in the same order. Caught by Holger Krug (hkrug@rationalizer.com).
* Applied patch submitted by Ryouichi Matsuda (r-matuda@sra.co.jp) that fixed ↵Barry Lind2002-01-15
| | | | a problem with leading zeros being lost on fractional seconds when setting a timestamp value on a PreparedStatement.
* Applied patch from Ryouichi Matsuda <r-matuda@sra.co.jp> where the jdbcBarry Lind2002-01-15
| | | | | driver was not properly handling timestamptz datatype when using the getObject() method on ResultSet. Fix adds this datatype to the object mappings.
* Manual page improvements.Bruce Momjian2002-01-15
|
* More cleanups.Bruce Momjian2002-01-15
|
* pg_upgrade doesn't live here anymore. Remove dangling references.Tom Lane2002-01-15
|
* Keep pg_upgrade as disabled.Bruce Momjian2002-01-15
|
* More wording improvements.Bruce Momjian2002-01-15
|
* More updates.Bruce Momjian2002-01-15
|
* Remove old pg_upgrade script, from Tom.Bruce Momjian2002-01-15
|
* More cleanups with ideas from Peter.Bruce Momjian2002-01-15
|
* Add Peter's portability and option suggestions.Bruce Momjian2002-01-15
|
* Update permissions?Bruce Momjian2002-01-14
|
* Reduce severity of 'XLogFlush: request is not satisfied' error condition,Tom Lane2002-01-14
| | | | | | per my proposal of a couple days ago. This will eliminate the unable- to-restart-database class of problem that we have seen reported half a dozen times with 7.1.*.
* Ensure that ecpg/test is cleaned by higher-level 'make clean'.Tom Lane2002-01-14
|
* Add README file.Bruce Momjian2002-01-14
|
* Doc improvements.Bruce Momjian2002-01-14
|
* Add manual page to /contrib. SGML from docs.Bruce Momjian2002-01-14
|
* Move pg_upgrade to /contrib. Still need to make Peter's portabilityBruce Momjian2002-01-14
| | | | changes.
* Small AIX fixes from Rick Flower.Bruce Momjian2002-01-14
|
* tag as beta 5 for *hopefully* a very very short beta cycle on this one?REL7_2_BETA5PostgreSQL Daemon2002-01-14
|
* Fix recreation of sequence files for 7.2 also because of XID change fromBruce Momjian2002-01-13
| | | | beta4 to beta5.
* - Fixed variable handling for struct members.Michael Meskes2002-01-13
| | | | | - Removed check for array input. An attribut might store the complete array.
* Now works for 7.1 databases.Bruce Momjian2002-01-13
|
* Now tested on 7.2->7.2 migration; still disabled. Need 7.1 testing now.Bruce Momjian2002-01-13
|
* Keep it disabled.Bruce Momjian2002-01-13
|
* Wow, it actually worked for the regression database. More testing needed.Bruce Momjian2002-01-13
|
* Bump catversion to ensure people apply recent timestamp and sequenceTom Lane2002-01-12
| | | | fixes.
* Update horology expected results (this variant extrapolated by yoursTom Lane2002-01-12
| | | | truly; should be verified by someone with an appropriate system).
* Update horology expected results (this variant verified on HPUX).Tom Lane2002-01-12
|
* Repair bugs in declarations of routines to add timestamptz and interval.Thomas G. Lockhart2002-01-12
| | | | | | | | | Thanks to Bruce for spotting it and Tom Lane for diagnosing it. Since horology test output is changing anyway, add some date/time input tests to horology.sql. Some of these should move to the tests for the individual data types, and we perhaps should add an entire new test for "timezone" to allow manipulating the current time zone without risking damage to the results of other tests.
* Fix pg_dump to read-lock all tables to be dumped as soon as it's readTom Lane2002-01-11
| | | | | | | their names from pg_class. This considerably reduces the window wherein someone could DROP or ALTER a table that pg_dump is intending to dump. Not a perfect solution, but definitely an improvement. Per complaints from Marc Fournier; patch by Brent Verner with some kibitzing by Tom Lane.
* Code review for latest changes.Tom Lane2002-01-11
|
* More man pages improvements; also needed to test sgml build.Bruce Momjian2002-01-11
|
* Sync up.Bruce Momjian2002-01-11
|
* VACUUM must make sure that a HEAP_MARKED_FOR_UPDATE tuple gets markedTom Lane2002-01-11
| | | | | | | | as either HEAP_XMAX_COMMITTED or HEAP_XMAX_INVALID once the updating transaction is gone. Otherwise some other transaction may come along and try to test the commit status of t_xmax later --- which could be after VACUUM has recycled the CLOG status for that xact. Bug introduced in post-beta4 bug fix.
* Fix sequence creation to set the t_xmin of a sequence's tuple toTom Lane2002-01-11
| | | | | | | | | | | | FrozenTransactionId, not the XID of the creating transaction. Without this it's possible for a reference to a long-gone CLOG record to occur, per Christian Meunier's bug report of 10-Jan-02. Worse, the sequence tuple would become invisible to SELECTs after 2 billion transactions. Since the fix is applied during sequence creation it does not help existing databases, unless you drop and recreate every sequence. However, we intend to force initdb for 7.2RC1 anyway, to fix a pg_proc error, so I see no need to do more for this problem.
* Added Christof's fixes.Michael Meskes2002-01-11
|
* More testing, more cleanups.Bruce Momjian2002-01-11
|
* pg_resetxlog specifies log location in hex; more pg_upgrade testingBruce Momjian2002-01-11
| | | | improvments.
* More cleanups.Bruce Momjian2002-01-11
|
* *** empty log message ***Hiroshi Inoue2002-01-11
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-07 13:01:09 +0000