ITAGAKI Takahiro wrote:
>
> Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>
> > 1. changing SIGINT so that it cancels the current table instead of
> > shutting down the entire worker.
I applied this part of the patch, thanks.
In passing I noticed that apparently we are leaking memory, because the
v
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> 1. changing SIGINT so that it cancels the current table instead of
> shutting down the entire worker.
>
> 2. changing DROP TABLE and TRUNCATE so that they cancel an autovac
> worker by sending SIGINT.
Quite so.
> 3. change the interrupt code so that
ITAGAKI Takahiro wrote:
> ITAGAKI Takahiro <[EMAIL PROTECTED]> wrote:
>
> > Here is a patch that cancels autovacuum workers conflicting with
> > DROP TABLE, TRUNCATE and CLUSTER. It was discussed here:
> > http://archives.postgresql.org/pgsql-hackers/2007-06/msg00556.php
>
> I made an adjustment
ITAGAKI Takahiro <[EMAIL PROTECTED]> wrote:
> Here is a patch that cancels autovacuum workers conflicting with
> DROP TABLE, TRUNCATE and CLUSTER. It was discussed here:
> http://archives.postgresql.org/pgsql-hackers/2007-06/msg00556.php
I made an adjustment for the latest 'more autovacuum fixes'
Here is a patch that cancels autovacuum workers conflicting with
DROP TABLE, TRUNCATE and CLUSTER. It was discussed here:
http://archives.postgresql.org/pgsql-hackers/2007-06/msg00556.php
Before backends drop a table, they search autovacuum workers that
are running on the table. If found, they sen
