Re: Isn't non-TEST_AND_SET code long dead?

From: Mike Mascari <mascarm(at)mascari(dot)com>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Isn't non-TEST_AND_SET code long dead?
Date: 2000-09-02 21:35:17
Message-ID: 39B17295.328994E7@mascari.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The Hermit Hacker wrote:
>
> Yank her ...
>
> On Sat, 2 Sep 2000, Tom Lane wrote:
> > Kinda makes me wonder what other bit-rot has set in in the non-TAS
> > code, and whether we ought not just rip it out rather than try to
> > "maintain" exceedingly delicate code that's gone untested for years.
> > bufmgr.c, in particular, has behavior that's nontrivially different
> > when HAVE_TEST_AND_SET isn't defined --- who wants to promise that
> > that still works?
> >
> > regards, tom lane
> >

On a somewhat related note, what about the NO_SECURITY defines
strewn throughout the backend? Does anyone run the server with
NO_SECURITY defined? And if so, what benefit is that over just
running with everything owned by the same user?

Just curious,

Mike Mascari

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-09-02 23:33:42 Re: PL/Perl compilation error
Previous Message Martin Christensen 2000-09-02 21:05:45 Re: [Solved] SQL Server to PostgreSQL