From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | simon(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us |
Subject: | Re: unlogged tables |
Date: | 2010-12-18 18:45:31 |
Message-ID: | AANLkTimax_L3heKbsOzNMn2SnheToJTahzgP6bHQZRuS@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Dec 18, 2010 at 12:27 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Robert Haas wrote:
>
>> If there's any third-party code out there that is checking
>> rd_istemp, it likely also needs to be revised to check whether
>> WAL-logging is needed, not whether the relation is temp. The way
>> I've coded it, such code will fail to compile, and can be very
>> easily fixed by substituting a call to RelationNeedsWAL() or
>> RelationUsesLocalBuffers() or RelationUsesTempNamespace(),
>> depending on which property the caller actually cares about.
>
> Hmm... This broke the SSI patch, which was using rd_istemp to omit
> conflict checking where it was set to true. The property I care
> about is whether tuples in one backend can be read by an transaction
> in a different backend, which I assumed would not be true for
> temporary tables. Which of the above would be appropriate for that
> use?
RelationUsesLocalBuffers().
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2010-12-18 19:39:42 | Extensions, patch v20 (bitrot fixes) (was: Extensions, patch v19 (encoding brainfart fix)) |
Previous Message | Jan Urbański | 2010-12-18 18:33:00 | Re: exceptions not present in plpy with Python 3 |