I was looking into supporting synchronized scans for VACUUM, and I
noticed that we currently don't remove the reported scan location as
this post suggests:
http://archives.postgresql.org/pgsql-patches/2007-06/msg00047.php
There was some debate about whether it should be done, but I thought
that t
Jeff Davis <[EMAIL PROTECTED]> writes:
> I was looking into supporting synchronized scans for VACUUM, and I
> noticed that we currently don't remove the reported scan location as
> this post suggests:
> http://archives.postgresql.org/pgsql-patches/2007-06/msg00047.php
I thought the end conclusion
On Sat, 2008-05-31 at 22:01 -0400, Tom Lane wrote:
> I thought the end conclusion of that thread was to not do anything,
> on the grounds that
> (1) having new scans sometimes fail to join an existing syncscan
> herd would be a bad thing because of the resulting performance
> uncertainty;
> (2) par
Greetings,
I have developed a fairly simple patch to the pg_dump utility. It is
against version 8.3.1 source code.
I have added a new parameter, -w/--where=EXPR
This lets you specify an expression that will be used in a WHERE
clause when the data is dumped.
I have implemented and test
