Re: pgsql: Fix a couple of bugs in win32 shmem name generation: * Don't cut

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Fix a couple of bugs in win32 shmem name generation: * Don't cut
Date: 2008-07-05 09:34:18
Message-ID: 486F401A.8010700@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Alvaro Herrera wrote:
> Magnus Hagander wrote:
>> Tom Lane wrote:
>
>>> According to what you just told me, the original coding is storing the
>>> name in a "local namespace", which presumably means it won't conflict
>>> anyway. Ergo, the existing coding is simply broken and there's nothing
>>> we can do about it.
>> Local namespace = Session local, not process local. So it would properly
>> protect against two processes started in the same session. One session
>> is, for example, an interactive login. But not if they were started by
>> different users, since they'd be in different sessions.
>
> But those different users would not have access to the same set of
> files, so it wouldn't work anyway, right?

Depends on what permissions you set on the directory, obviously....
Default ones depend on windows version and where in the filesystem they go.

//Magnus

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message User H-saito 2008-07-06 15:08:21 psqlodbc - psqlodbc: Fixed has a default promotion can't match an empty
Previous Message User Bloodnok 2008-07-05 00:32:26 veil - veil: Initial release of changes for serialisation.

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-07-05 09:41:18 Re: Explain XML patch v2
Previous Message Hans-Juergen Schoenig 2008-07-05 08:43:57 Re: WITH RECURSIVE updated to CVS TIP