> There seems to a race condition somewhere where that if you're
> running let's say pg_dumpall and happen to drop a table mid-dump
> pg_dumpall will die because it looses the table.
>
> Would it make sense to use a transaction system so that when a table
> is renamed/dropped it doesn't actually go away until all transactions
> that started before the drop take place?
>
> one could do probably implement this using refcounts and translating
> dropped tables into temporary mangled names.
Imho if I dropped a table I would not like another session to still access
it,
so we should imho rather fix pg_dump.
Andreas
