| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
cturner@redhat.com.
|
| |
|
|
|
| |
It would try to call the input conversion routines for them anyway.
So, a valid input string for the datatype had to be supplied.
|
| |
|
|
| |
allows plperl routines to return NULL as intended.
|
| |
|
|
|
|
|
| |
removes any empty chunks, the chunk previously added won't be there
anymore, so it's possible there is zero free space in the rel's page list
afterwards. Must loop back and rerun the part that adds a chunk to
the list.
|
| | |
|
| |
|
|
|
| |
value of TCL_SHLIB_LD in the shell script that creates Makefile.tcldefs,
rather than trying to persude gmake to do it.
|
| | |
|
| |
|
|
|
|
| |
compile in client apps that use the standard installed header set.
To allow removing that include, move DLLIMPORT definitions out of c.h
and into the appropriate port-specific header files.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
tom lane
|
| |
|
|
| |
Previous versions did not correctly identify primary/foreign keys
|
| |
|
|
|
| |
dumped by pg_dump -o. Per bug report posted by Bruce; fix is from
Philip Warner, reviewed by Tom Lane.
|
| | |
|
| |
|
|
| |
cannot see a reason why it should be an error.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
the two trigger sets were logically equal, but not in the same order.
Caught by Holger Krug (hkrug@rationalizer.com).
|
| |
|
|
| |
a problem with leading zeros being lost on fractional seconds when setting a timestamp value on a PreparedStatement.
|
| |
|
|
|
| |
driver was not properly handling timestamptz datatype when using the
getObject() method on ResultSet. Fix adds this datatype to the object mappings.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.*.
|
| | |
|
| | |
|
| |
|
|
| |
beta4 to beta5.
|
| |
|
|
|
| |
- Removed check for array input. An attribut might store the
complete array.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
fixes.
|
| |
|
|
| |
truly; should be verified by someone with an appropriate system).
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
| |
improvments.
|
| | |
|
| | |
|
| |
|
|
| |
anymore.
|
