From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: including backend ID in relpath of temp rels - updated patch |
Date: | 2010-09-15 16:46:07 |
Message-ID: | AANLkTikL-EF+p0YYzMi4e3d52zVYE9RTUWvAd=dqPpaj@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 15, 2010 at 12:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Wed, Sep 15, 2010 at 12:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> The above scenario is only a risk if you suppose that dropping a
>>> relation that lacks physical storage will nonetheless result in
>>> attempted unlink()s. I think that that's probably not the case;
>
>> Why? How would we know that it didn't have physical storage prior to
>> attempting the unlinks?
>
> From the relkind.
Oh, sure, I agree with you in that specific case.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2010-09-15 16:47:34 | Re: Sync Replication with transaction-controlled durability |
Previous Message | Robert Haas | 2010-09-15 16:45:43 | Re: [HACKERS] Re: pgsql: Use a latch to make startup process wake up and replay |