From: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: unlogged tables |
Date: | 2010-11-15 17:45:25 |
Message-ID: | AANLkTinhMkhOCCxJpjgSZ5d9Fe1vgFnAgZ=SnyxF1csQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Nov 15, 2010 at 11:22 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Yeah, this infrastructure doesn't really allow that. The truncate
> happens way too early on in startup to execute any user-provided code.
But you could use the very feature of unlogged tables to know if
you've "initialized" some unlogged table by using an unlogged table to
note the initilization.
If the value you expect isn't in your "noted" table, you know that
it's been truncated...
Sure, it's "app side", but the hole point of unlogged tables it to
allow optimzations when the "appside" knows the data's dispensable and
rebuild-able.
a.
--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-11-15 17:48:58 | Re: Count backend self-sync calls |
Previous Message | Robert Haas | 2010-11-15 17:32:49 | Re: unlogged tables |