Re: to_char incompatibility

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: josh(at)agliodbs(dot)com
Cc: "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: to_char incompatibility
Date: 2008-01-14 22:48:04
Message-ID: 7681.1200350884@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> writes:
> Security Definer has ramifications in PostgreSQL which I don't think it
> does in Oracle. Particularly, see:
> http://www.postgresql.org/docs/techdocs.77

BTW, that article needs to be updated to show the (much easier) way to
do it as of 8.3.

I concur that "make all your functions security definer by default" is
unlikely to make a system more secure overall --- it'll just move the
problems around. Especially if it's applied blindly by someone who
stopped reading at that point.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-01-14 23:16:08 Re: Bug: Unreferenced temp tables disables vacuum to update xid
Previous Message Tom Lane 2008-01-14 22:20:54 Re: SSL over Unix-domain sockets