From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ben <bench(at)silentmedia(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: autovacuum vs. createdb |
Date: | 2008-01-16 00:01:56 |
Message-ID: | 15252.1200441716@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ben <bench(at)silentmedia(dot)com> writes:
> I'm noticing a problem where autovacuum touching template1 when createdb
> is run is making createdb fail. That's easy to work around when doing
> things by hand (just run it again), but when running createdb with a
> script, it's not so clear to me how to keep things working all the time.
There's a fix for this in 8.3, but in existing releases about all you
can do is make your script wait a few seconds and retry.
> One thought I had was having my script insert rows into pg_autovacuum
> temporarily (I assume in template1) but I'm not sure what tables I need to
> tell the autovacuum daemon to keep away from.
That seems counterproductive: any churn you make in template1 will mean
that autovacuum actually has something to do there, which you don't
want.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | T.J. Adami | 2008-01-16 00:07:21 | Re: COUNT() with ORDER BY |
Previous Message | Clodoaldo | 2008-01-15 23:56:21 | Re: ATTN: Clodaldo was Performance problem. Could it be related to 8.3-beta4? |