Re: [HACKERS] DROP TABLE inside transaction block

>
> Michael Simms <grim(at)argh(dot)demon(dot)co(dot)uk> writes:
> >> (Of course, what would be really nice is if it just worked, but I don't
> >> see any way to make that happen without major changes. Simply
> >> postponing the unlink to end of transaction isn't workable; consider
> >> BEGIN; DROP TABLE foo; CREATE TABLE foo; ...)
>
> > Cant you just rename to a unique name, maybee in another directory,
>
> Not if other backends are also accessing the table. Remember that to
> make this really work, the DROP would have to be invisible to other
> backends until commit.

Could you not then:

send a notification to all other backends

Put something into the table header that any new backend that tries to use it
is informed that the correct table is stored elsewhere.

I dont know, Im just throwing ideas here {:-)

Michael Simms