Yeah, this is possible because DROP TABLE does not attempt to acquire
exclusive lock on the victim table's parent(s). So if a concurrent
query operating on the parent had already obtained the victim table's
OID from pg_inherit, it would get this failure.
It's somewhat annoying but I'm not sure
On Thu, 2009-05-14 at 00:14 -0500, Jaime Casanova wrote:
> is this a bug of some kind?
Yes. Installing a buggy version is a bug of some kind ;)
--
Devrim GÜNDÜZ, RHCE
Command Prompt - http://www.CommandPrompt.com
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
Thomas Johansson writes:
> So what would be the best/easiest way to circumvent this behaviour
> while still allowing concurrent queries? I tried to implement a solution
> which I hoped would fix this by first doing NO INHERIT on the partition
> which were to be dropped and then later (an hour
Me rindo
Llevo una semana tratando de instalar postgres
y simplemente es demasiado difícil, es más fácil
cambiar a otra base de datos
2009/5/14 Hugo
> Me rindo
>
> Llevo una semana tratando de instalar postgres
> y simplemente es demasiado difícil, es más fácil
> cambiar a otra base de datos
>
Sorry to hear that you 'surrender' ! I'm not really sure you've
provided any information to help us with your problem though, may
