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

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Mike Mascari <mascarm(at)mascari(dot)com>, The Hermit Hacker <scrappy(at)hub(dot)org>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Isn't non-TEST_AND_SET code long dead?
Date: 2000-10-16 17:08:34
Message-ID: 200010161708.NAA19626@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Mike Mascari <mascarm(at)mascari(dot)com> writes:
> > 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?
>
> I suppose the idea was to avoid expending *any* cycles on security
> checks if you didn't need them in your particular situation. But
> offhand I've never heard of anyone actually using the feature. I'm
> dubious whether the amount of time saved would be worth the trouble.

NO_SECURITY define removed.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-10-16 17:10:31 Re: Yet another LIKE-indexing scheme
Previous Message Bruce Momjian 2000-10-16 17:03:32 Re: Yet another LIKE-indexing scheme