| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fun fact about autovacuum and orphan temp tables |
| Date: | 2016-09-06 16:21:39 |
| Message-ID: | ef118ae5-7e96-6470-0fe9-88fda5f9714f@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/5/16 12:14 PM, Bruce Momjian wrote:
>> > I have certainly faced my fair share of customers with dangling temp
>> > tables, and would like to see this changed in some way or another.
> I don't think we look at those temp tables frequently enough to justify
> keeping them around for all users.
Plus, if we cared about forensics, we'd prevent re-use of the orphaned
schemas by new backends. That doesn't seem like a good idea for normal
use, but if we had a preserve_orphaned_temp_objects GUC someone could
add that behavior.
Isn't there some other GUC aimed at preserving data for forensics
(besides zero_damaged_pages)? Maybe we could just broaden that to
include orphaned temp objects.
--
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-09-06 16:41:48 | Re: Bug in 9.6 tuplesort batch memory growth logic |
| Previous Message | Peter Eisentraut | 2016-09-06 16:19:31 | Re: [COMMITTERS] pgsql: Make initdb's suggested "pg_ctl start" command line more reliabl |