From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, alexk <alexk(at)commandprompt(dot)com>, Alexander Shulgin <ash(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Postmaster holding unlinked files for pg_largeobject table |
Date: | 2011-06-09 17:59:00 |
Message-ID: | 1307642259-sup-7269@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Excerpts from Tom Lane's message of mié jun 08 14:28:02 -0400 2011:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Okay, here's a patch implementing this idea. It seems to work quite
> > well, and it solves the problem in a limited testing scenario -- I
> > haven't yet tested on the customer machines.
>
> This seems mostly sane, except I think you have not considered the
> issue of when to clear the smgr_transient flag on an existing
> SMgrRelation: if it starts getting used for "normal" accesses after
> having by chance been used for a blind write, we don't want the
> transient marking to persist. That's why I suggested having smgropen
> always clear it.
>
> Likewise, I think the FD_XACT_TRANSIENT flag on a VFD needs to go away
> at some point, probably once it's actually been closed at EOXACT, though
> there's doubtless more than one way to handle that.
Aha, I see -- makes sense. Here's an updated patch.
> > This customer is running on 8.4 so I started from there; should I
> > backpatch this to 8.2, or not at all?
>
> I'm not excited about back-patching it...
Bummer.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Attachment | Content-Type | Size |
---|---|---|
smgr-transient-files-2.patch | application/octet-stream | 11.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2011-06-09 18:00:19 | Re: postgres server on windows with high availability and failover safe |
Previous Message | Greg Smith | 2011-06-09 17:44:04 | Re: [GENERAL] [PERFORMANCE] expanding to SAN: which portion best to move |
From | Date | Subject | |
---|---|---|---|
Next Message | Florian Pflug | 2011-06-09 18:00:31 | Re: Bug in XPATH() produces invalid XML values and probably un-restorable dumps |
Previous Message | Robert Haas | 2011-06-09 17:55:02 | Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS |