| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
The previous coding treated anything that wasn't an autovacuum launcher
as a normal backend, which is wrong now that we also have WAL senders.
Fujii Masao, reviewed by Robert Haas, Alvaro Herrera, Tom Lane,
and Bernd Helmle.
|
|
|
|
|
|
|
|
|
| |
The new coding avoids a spurious debug message when a transaction
that has changed the isolation level has been rolled back. It also
allows the property to be freely changed to the current value within
a subtransaction.
Kevin Grittner, with one small change by me.
|
|
|
|
|
|
| |
Un-break Windows build (I hope) by making the HAVE_FSYNC_WRITETHROUGH
code match the backend. Fix incorrect program help message. static-ize
all functions.
|
|
|
|
|
|
| |
Actually rename the program, rather than just claiming we did. Hook it
into the build system. Get rid of useless dependency on libpq. Clean up
#include list and messy whitespace.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The way the exception types where added to the module was wrong for
Python 3. Exception classes were not actually available from plpy.
Fix that by factoring out code that is responsible for defining new
Python exceptions and make it work with Python 3. New regression test
makes sure the plpy module has the expected contents.
Jan Urbanśki, slightly revised by me
|
|
|
|
| |
Jeff Turner
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
foreign table. We check for usage privileges on the foreign server, that ought
to be enough.
Shigeru HANADA
|
|
|
|
|
|
|
|
| |
Failure to do so can lead to constraint violations. This was broken by
commit 1ddc2703a936d03953657f43345460b9242bbed1 on 2010-02-07, so
back-patch to 9.0.
Noah Misch. Regression test by me.
|
|
|
|
| |
Hitoshi Harada
|
|
|
|
| |
Hitoshi Harada
|
|
|
|
|
|
| |
This makes PLy_procedure_create a bit more manageable.
Jan Urbański
|
|
|
|
|
| |
Original patch by Fernando Ike, revived by Josh Kuperschmidt, reviewed by Andreas
Karlsson, and in earlier versions by Tom Lane and Peter Eisentraut.
|
|
|
|
| |
Peter Geoghegan, reviewed by Stephen Frost
|
|
|
|
| |
Thom Brown
|
|
|
|
| |
Jan Urbański, reviewed by Peter Eisentraut, Álvaro Herrera, Tom Lane :-)
|
|
|
|
| |
Jan Urbański
|
|
|
|
|
|
| |
The previous code would try to print out a null pointer.
Jan Urbański
|
|
|
|
|
|
| |
The latter is undocumented and the speed gain is negligible.
Jan Urbański
|
|
|
|
|
|
|
|
| |
Pay attention to the attisdropped field and skip over TupleDesc fields
that have it set. Not a real problem until we get table returning
functions, but it's the right thing to do anyway.
Jan Urbański
|
|
|
|
|
|
|
| |
As discussed, even if the PL needs a permanent memory location, it
should use palloc, not malloc. It also makes error handling easier.
Jan Urbański
|
|
|
|
|
|
|
|
|
| |
If the function using yield to return rows fails halfway, the iterator
stays open and subsequent calls to the function will resume reading
from it. The fix is to unref the iterator and set it to NULL if there
has been an error.
Jan Urbański
|
|
|
|
| |
add more test cases for open_sync of different sizes.
|
|
|
|
|
|
|
|
|
|
| |
We can get the length of a compressed or out-of-line datum without actually
detoasting it. If the lengths of two strings are unequal, we can then
conclude they are unequal without detoasting. That saves considerable work
in an admittedly less-common case, without costing anything much when the
optimization doesn't apply.
Noah Misch
|
|
|
|
|
| |
Previously we'd always log replication connections, with no
way to turn them off.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
documentation.
Ray Stell
Also fix some libpq title capitalization problems.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Two separate hash tables are used for regular procedures and for
trigger procedures, since the way trigger procedures work is quite
different from normal stored procedures. Change the signatures of
PLy_procedure_{get,create} to accept the function OID and a Boolean
flag indicating whether it's a trigger. This should make implementing
a PL/Python validator easier.
Using HTABs instead of Python dictionaries makes error recovery
easier, and allows for procedures to be cached based on their OIDs,
not their names. It also allows getting rid of the PyCObject field
that used to hold a pointer to PLyProcedure, since PyCObjects are
deprecated in Python 2.7 and replaced by Capsules in Python 3.
Jan Urbański
|
|
|
|
|
|
|
|
|
|
|
| |
If the slice to be assigned to was before the existing array lower bound
(requiring at least one null element to spring into existence to fill the
gap), the code miscalculated how many entries needed to be copied from
the old array's null bitmap. This could result in trashing the array's
data area (as seen in bug #5840 from Karsten Loesing), or worse.
This has been broken since we first allowed the behavior of assigning to
non-adjacent slices, in 8.2. Back-patch to all affected versions.
|
|
|
|
|
| |
Per bug #5835 by Julien Demoor
Author: Alex Hunsaker
|
| |
|
|
|
|
|
| |
Makes replication slaves identify themselves in the new
pg_stat_replication view.
|
|
|
|
|
|
| |
Otherwise WAL recovery will replay the un-flushed WAL after walreceiver has
exited, which can lead to a non-recoverable standby if the system crashes hard
at that point.
|
| |
|
|
|
|
| |
error reporting to be more consistent.
|
| |
|
|
|
|
| |
Postgres, and cases where o_direct does not work with certain file systems.
|
| |
|
| |
|
|
|
|
| |
wal_sync_method on Linux.
|
|
|
|
| |
and it can be enhanced easier.
|
|
|
|
|
|
|
|
|
|
| |
This closes a race condition where if a tablespace was created
after the enumeration happened but before the do_pg_start_backup()
was called, the backup would be incomplete. Now that it's done
while we are in backup mode, WAL replay will recreate it during
restore.
Noted by Heikki.
|
| |
|
|
|
|
| |
Adjusted patch by Josh Berkus
|
|
|
|
|
|
|
|
|
| |
backend, as far as the postmaster shutdown logic is concerned. That means,
fast shutdown will wait for WAL sender processes to exit before signaling
bgwriter to finish. This avoids race conditions between a base backup stopping
or starting, and bgwriter writing the shutdown checkpoint WAL record. We don't
want e.g the end-of-backup WAL record to be written after the shutdown
checkpoint.
|