Hackers,
Here is a doc patch that includes pages for savepoint commands. It
would be cool if they can be applied as starting points for savepoint
documentation. Poeple who can do better, please feel free to improve in
any way.
--
Alvaro Herrera (alvherre[a]dcc.uchile.cl)
Cómo ponemos nuestros
This is the known patch, with following changes:
- realStdErr handed over for EXEC_BACKEND, but still not tested
- Sometimes EMFILE is received in the logger's process queue, when a
backend ended after a SSL connection was interrupted. This is ignored
now (previously it forced an exit(1) and
These files add administrative functions to pgsql 7.5. All are used by
pgAdmin3 or will be used in the near future if available. This is meant
as contrib module, whilst IMHO all these functions should be integrated
into the backend.
Included are functions to
log file access
These where
Claudio Natoli wrote:
Seems inconsistent to me.
There is no inconsistency, as the two requirements are aimed at very
different issues. It was just the case that one (win32 versioning) was
inadvertently a potential (and rejected) solution to the other (auto version
check).
The question
Alvaro Herrera [EMAIL PROTECTED] writes:
Nesting level report via a ParameterStatus message sent just before
ReadyForQuery (Z message).
Hasn't this really been obsoleted by events? In the SAVEPOINT world
I doubt that it's needed.
regards, tom lane
Alvaro Herrera [EMAIL PROTECTED] writes:
Here is a patch that fixes some of the TODO items in the nested xacts
list:
handle large objects
On the large-objects stuff: it seems like a really bad idea to be
fooling with CurrentResourceOwner like that. What that means is that if
a subtransaction
Alvaro Herrera [EMAIL PROTECTED] writes:
There are some likely controversial changes; the Xid caches, in the
first place.
No kidding ;-)
Do you have any theoretical or practical evidence for the usefulness of
the negxids cache? Seems to me the shared memory space would be better
spent on
The attached patch allows the specification of the tablespace the index
is to be created in for unique and pk constraints. It also fixes the
dumping of such constraints so that they are restored into the correct
tablespace, after they have been moved with SET TABLESPACE. This is
currently an
