Log Message:
---
Fix two race conditions between the pending unlink mechanism that was put in
place to prevent reusing relation OIDs before next checkpoint, and DROP
DATABASE. First, if a database was dropped, bgwriter would still try to unlink
the files that the rmtree() call by the DROP D
Log Message:
---
Fix two race conditions between the pending unlink mechanism that was put in
place to prevent reusing relation OIDs before next checkpoint, and DROP
DATABASE. First, if a database was dropped, bgwriter would still try to unlink
the files that the rmtree() call by the DROP D
Log Message:
---
Cause EXPLAIN's VERBOSE option to print the target list (output column list)
of each plan node, instead of its former behavior of dumping the internal
representation of the plan tree. The latter display is still available for
those who really want it (see debug_print_plan)
Gregory Stark <[EMAIL PROTECTED]> writes:
> Does this do the right thing if all the columns in the physical target list
> are in fact present in the target list?
Yeah, it's pretty much a no-op in that case.
regards, tom lane
--
Sent via pgsql-committers mailing list (pgs
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Log Message:
> ---
> Fix a couple of oversights associated with the "physical tlist" optimization:
> we had several code paths where a physical tlist could be used for the input
> to a Sort node, which is a dumb idea because any unneeded table colum
Log Message:
---
Clean up a few places where Datums were being treated as pointers (and vice
versa) without going through DatumGetPointer.
Gavin Sherry, with Feng Tian.
Modified Files:
--
pgsql/src/backend/access/common:
heaptuple.c (r1.120 -> r1.121)
(htt
Log Message:
---
Fix a couple of oversights associated with the "physical tlist" optimization:
we had several code paths where a physical tlist could be used for the input
to a Sort node, which is a dumb idea because any unneeded table columns will
increase the volume of data the sort has t
Log Message:
---
Fix a couple of oversights associated with the "physical tlist" optimization:
we had several code paths where a physical tlist could be used for the input
to a Sort node, which is a dumb idea because any unneeded table columns will
increase the volume of data the sort has t
Log Message:
---
TODO Done:
> * -Allow administrators to safely terminate individual sessions
Modified Files:
--
pgsql/doc:
TODO (r1.2424 -> r1.2425)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/TODO?r1=1.2424&r2=1.2425)
pgsql/doc/src/FAQ:
Log Message:
---
Re-enable pg_terminate_backend() using SIGTERM. SIGTERM testing still
needed.
Modified Files:
--
pgsql/doc/src/sgml:
func.sgml (r1.432 -> r1.433)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml?r1=1.432&r2=1.433)
Log Message:
---
Add some code to EXPLAIN to show the targetlist (ie, output columns)
of each plan node. For the moment this is debug support only and is
not enabled unless EXPLAIN_PRINT_TLISTS is defined at build time.
Later I'll see about the idea of letting EXPLAIN VERBOSE do it.
Modif
11 matches
Mail list logo
