Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Alvaro Herrera" <alvherre(at)dcc(dot)uchile(dot)cl>, "Gavin Sherry" <swm(at)linuxworld(dot)com(dot)au>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Philip Warner" <pjw(at)rhyme(dot)com(dot)au>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?
Date: 2004-05-03 14:29:43
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE34B8FE@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I'm not sure how would one "send to the other backends."
> Maybe write another file on disk, one for each remote
> backend? Surely this can be done somehow. I've heard that
> on linux-2.6 they are implementing "POSIX message queues"
> (not sure what those are anyway); maybe we can do that on
> platforms that support it, for performance.

Dunno if this is relevant, but if you want to go with message queues,
there is also SystemV message queues. Since postgresql already uses sysv
semaphores and shared memory, this would perhaps be portable to more
systems that pg supports today (though you'd still need some kind of
abstraction layer, since e.g. win32 does not have it).
(man msgsnd, msgrcv, msgctl, msgget

//Magnus

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Sherry 2004-05-03 14:30:57 Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?
Previous Message Tom Lane 2004-05-03 14:13:38 Re: ANALYZE locks pg_listener in EXCLUSIVE for long time?