Re:

From: Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it>
To: Luca Ferrari <fluca1978(at)infinito(dot)it>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re:
Date: 2013-07-15 06:33:02
Message-ID: CAHjZ2x6-Pi7Go=_7A4-VvNj=EaXN8k=den9osQ0k8L8+JTCphw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2013/7/15 Luca Ferrari <fluca1978(at)infinito(dot)it>:
> On Sun, Jul 14, 2013 at 8:36 PM, Vincenzo Romano
> <vincenzo(dot)romano(at)notorand(dot)it> wrote:
>
>> I am only concerned about how late is done the binding between a table
>> name and the actual OID for other functions, views and triggers.
>
>
> Well, it should work like this: once the parser decides that a query
> looks good, it seaches for the catalogue to find out all the names of
> implied relations. Therefore, the binding you mention should happen as
> late as possible. However, I'm not sure if there a kind of caching
> mechanism that can invalidate such sentence. Someone with more
> experience can detail better.
>
> Luca

That's exactly my fear in doing that transactional DDL.
And it's not just the table names, but also the structure, the
indexes, the statistics and so on.
Is there anyone on this ML who "owns" the truth? :-)

The alternative is to do things the "good ol' way" by DELETING+INSERTING
(http://tapoueh.org/blog/2013/07/05-archiving-data-fast.html)
Where I'd fear for longer LOCKs.

In response to

  • Re: at 2013-07-15 06:13:25 from Luca Ferrari

Responses

  • Re: at 2013-07-15 08:44:09 from Luca Ferrari

Browse pgsql-general by date

  From Date Subject
Next Message David Welton 2013-07-15 08:33:35 Re: V8.4 TOAST table problem
Previous Message Sergey Konoplev 2013-07-15 06:16:24 Re: Transaction control in shards through PLPROXY