aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* - 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.
* 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
|
* More updates for int8 sequence restoration. Old dump file not requiredBruce Momjian2002-01-11
| | | | anymore.
* Handle int4-int8 sequence migration without full data dump.Bruce Momjian2002-01-11
|
* Add a directory to save the changes until 7.3-tree is branched.Hiroshi Inoue2002-01-11
|
* More improvements using pg_resetxlog. still disabled.Bruce Momjian2002-01-11
|
* Include sqlca.h automatically.Michael Meskes2002-01-10
|
* More pg_upgrade improvements. Almost done, except for max transactionBruce Momjian2002-01-10
| | | | setting.
* More improvements; still disabled. (Don't panic.)Bruce Momjian2002-01-10
|
* The result of getopt() should be compared to -1, not EOF, perTom Lane2002-01-10
| | | | pgsql-hackers discussion of this date.
* Update with new features. Still disabled.Bruce Momjian2002-01-09
|
* Fix use of 'char' to hold result of getc, per bug report forwarded byTom Lane2002-01-09
| | | | Oliver Elphick. A few other minor cleanups while at it.
* Fix portability problem (result of getopt is int, not char).Tom Lane2002-01-09
|
* Remove clog copy.Bruce Momjian2002-01-09
|
* Make improvements to pg_upgrade; is still disabled.Bruce Momjian2002-01-09
|
* Add quotes around $bindir.Bruce Momjian2002-01-09
|
* Fix include paths for case of VPATH build.Tom Lane2002-01-09
|
* make install failed in VPATH build.Tom Lane2002-01-08
|
* Fix copy-and-paste mistake exposed by gcc warning.Tom Lane2002-01-08
|
* In a VPATH build, resultmap must be one of the symlinked files, elseTom Lane2002-01-08
| | | | | pg_regress doesn't see it and you don't get any port-specific comparisons.
* Revert last change (CFLAGS+=-g). Probably was a mistake...Peter Eisentraut2002-01-08
|
* Remove shift/reduce conflicts introduced by last change.Tom Lane2002-01-08
|
* Fix lpad() and rpad() to produce correct results in variable-lengthTom Lane2002-01-08
| | | | multibyte encodings.
* Fixed array pointers, no longer using void * in arithmetics.Michael Meskes2002-01-08
|
* Tweak LWLock algorithms so that an awakened waiter for a lock is notTom Lane2002-01-07
| | | | | | | | | | | | | | | granted the lock when awakened; the signal now only means that the lock is potentially available. The waiting process must retry its attempt to get the lock when it gets to run. This allows the lock releasing process to re-acquire the lock later in its timeslice. Since LWLocks are usually held for short periods, it is possible for a process to acquire and release the same lock many times in a timeslice. The old spinlock-based implementation of these locks allowed for that; but the original coding of LWLock would force a process swap for each acquisition if there was any contention. Although this approach reopens the door to process starvation (a waiter might repeatedly fail to get the lock), the odds of that being a big problem seem low, and the performance cost of the previous approach is considerable.
* Fixed parser to accept initializing expressions starting with "(".Michael Meskes2002-01-07
|
* Editorial reviewPeter Eisentraut2002-01-07
|
* If we fail to fork a new backend process, (try to) report the failureTom Lane2002-01-06
| | | | | | to the client before closing the connection. Before 7.2 this was done correctly, but new code would simply close the connection with no report to the client.
* Add CHECK_FOR_INTERRUPTS() in various strategic spots, per commentsTom Lane2002-01-06
| | | | from Hiroshi.
* Bugfix for bug reported by Marcus Better (marcus@dactylis.com). When preformingBarry Lind2002-01-05
| | | | | | a get on a bytea value the code was running the raw value from the server through character set conversion, which if the character set was SQL_ASCII would cause all 8bit characters to become ?'s.
* Fix some incorrect and obsolete commentary.Tom Lane2002-01-04
|
* Have to_date() call timestamptz_date() per Karel's email instructions.Thomas G. Lockhart2002-01-04
| | | | | | | Fixes time zone problems introduced by Thomas' implementation of TIMESTAMP WITHOUT TIME ZONE which caused the behavior of the previously appropriate routine, timestamp_date(), to change for the worse in this context.
* Replace #ifdef, #endif with # requires comment.Bruce Momjian2002-01-04
|
* Require ownership permission for CREATE INDEX, per bug report.Tom Lane2002-01-03
| | | | | | | | | Disallow CREATE INDEX on system catalogs, non-tables (views, sequences, etc). Disallow CREATE/DROP TRIGGER on system catalogs, non-tables. Disallow ALTER TABLE ADD/DROP CONSTRAINT on system catalogs. Disallow FOREIGN KEY reference to non-table. None of these things can actually work in the present system structure, but the code was letting them pass without complaint.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-07 05:30:40 +0000