| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | "Constantin S(dot) Pan" <kvapen(at)gmail(dot)com>, Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fun fact about autovacuum and orphan temp tables |
| Date: | 2016-10-21 15:15:21 |
| Message-ID: | e2973b17-32dd-6741-1b3c-b41b052103d8@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/21/16 8:47 AM, Tom Lane wrote:
>> It seems to me that you'd even want to make the drop of orphaned
>> > tables mandatory once it is detected even it is not a wraparound
>> > autovacuum.
> If we are willing to do that then we don't really have to solve the
> problem on the backend side. One could expect that autovacuum would
> clean things up within a few minutes after a backend failure.
Unless all the autovac workers are busy working on huge tables... maybe
a delay of several hours/days is OK in this case, but it's not wise to
assume autovac will always get to something within minutes.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-10-21 15:20:57 | Re: Aggregate Push Down - Performing aggregation on foreign server |
| Previous Message | Robert Haas | 2016-10-21 15:12:43 | Re: Aggregate Push Down - Performing aggregation on foreign server |