On Tue, 2002-05-07 at 15:31, Tom Lane wrote:
> mlw <[EMAIL PROTECTED]> writes:
> > In the current CVS directory, there is pgsql/src/backend/port directory.
>
> > I propose that this become a separate subproject and library.
>
> Right offhand, that seems a pointless exercise in relabeling code th
mlw <[EMAIL PROTECTED]> writes:
> I did, and yes I was confused. Sorry. Your posix implementation assumes that
> only a single process will have access to the semaphore list for deletion is
> this correct? I guess I need to know how much access the child processes need
> to have to the internal co
Matthew Kirkwood <[EMAIL PROTECTED]> writes:
>> ... and we already do it. But it protects the port number, not
>> the data directory.
> If I understood him correctly, Marc was suggesting a further
> domain socket inside the data directory.
Right, and that would work because we would reference i
<[EMAIL PROTECTED]> writes:
> Aside from being a near-universal "best practice", it makes it easier for
> someone to analyze whether local patches to 7.2.1 conflict with work that
> the team has committed.
There is a 7.2 branch, and I would think that the tip of that branch is
generally what you
Tom Lane wrote:
> And no, I don't want to undo those changes. Especially not if the
> only reason for it is to not have to use Cygwin on Windows. Most
> of these changes made the startup code substantially simpler,
> faster, and more reliable.
Then I think the notion of a pure Windows version i
Tom Lane wrote:
> BTW, I have been able to test the named-semas variant of posix_sema.c
> on OS X, and it works. I don't have access to any platforms that
> support unnamed POSIX semas, which is too bad because that seems much
> the preferable variant. Can anyone check it out?
I did, and yes I
Doesn't appear that pg_sema is picking up the semaphore implementation
on FreeBSD.
bash-2.05a$ uname -a
FreeBSD knight.zort.ca 4.5-RELEASE FreeBSD 4.5-RELEASE #3: Sun Feb 3
22:26:40 EST 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/KNIGHT i386
In file included from ../../../../src/includ
Mark kirkwood <[EMAIL PROTECTED]> writes:
> I ran 10 threads in 2) and saw my database grow from the initial size of
> 150M by about 1G per hour (I stopped my test after 5 hours @ 4.5G).
Which files grew exactly? (Main table, indexes, toast table, toast index?)
Was the FSM size parameter set la
> I'd like to contribute new code for Postgres geometry type 'path' operations
> (including line buffer). Where should I send this?
Send to [EMAIL PROTECTED] It may be helpful to (i.e. please
do) post a summary of what you are intending to send to this mailing
list so folks have an idea of what i
On Tue, 7 May 2002, Tom Lane wrote:
> > Nobody actually needs to connect to the socket. Simple,
> > race-free, 10 lines of code.
>
> ... and we already do it. But it protects the port number, not
> the data directory.
If I understood him correctly, Marc was suggesting a further
domain socket i
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> I see there are routines doing similar things but for functions and
> others. I'm right in saying that OID isn't unique in a database
> (necessarily) and so we couldn't have a general object_is_visible(oid)
> function that did the appropiate from th
mlw <[EMAIL PROTECTED]> writes:
> In the current CVS directory, there is pgsql/src/backend/port directory.
> I propose that this become a separate subproject and library.
Right offhand, that seems a pointless exercise in relabeling code that's
going to be the same either way. What's the actual
Matthew Kirkwood <[EMAIL PROTECTED]> writes:
> Nobody actually needs to connect to the socket. Simple,
> race-free, 10 lines of code.
... and we already do it. But it protects the port number, not
the data directory.
regards, tom lane
---(end of
As I set out to do the Windows semaphore thing, I notice it can get quite ugly.
In the current CVS directory, there is pgsql/src/backend/port directory.
I propose that this become a separate subproject and library. The reason I want
this is because the semaphore support, specifically multiple se
Hello,
I'd like to contribute new code for Postgres geometry type 'path' operations
(including line buffer). Where should I send this?
---
Alex Shevlakov,
Motivation Free Software consulting,
Moscow, Russia
---
http://motivation.ru
msg16797/pgp0.pgp
Description: PGP signa
Hi Alvaro, Hi Nigel,
Thanks for your reply. I indeed already tried with a plpgsql function. But
that's just my problem : if I call a function from within a view's rule,
this function is not executed anymore with the same rights as a user had on
the view. So if a user may access a view, but not th
On Sun, 5 May 2002, Lamar Owen wrote:
> On Sunday 05 May 2002 02:46 pm, Jack Bates wrote:
> > CVSROOT=:pserver:[EMAIL PROTECTED]:/projects/cvsroot
>
> > Still no tag for 7.2.1.
>
> > Could I (again) request that a tag be set for the current public release
> > of this product?
>
> Why? ...
Aside
On Mon, 6 May 2002, Tom Lane wrote:
> > As a backend is started up, connect to that socket ... if socket is open
> > when trying to start a new frontend, fail as there are currently other
> > connections attached to it?
>
> But the backends would only have the socket open, they'd not be
> activel
On Mon, 6 May 2002, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > For this if we look once again at RelnameGetRelid(relname) in
> > backend/catalog/namespace.c wouldn't this is_visible() function simply be a
> > wrapper around it?
>
> Sort of. It's there already, see Rela
19 matches
Mail list logo