Re: Re: [PATCHES] Fw: Isn't pg_statistic a security hole - Solution Proposal - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Re: [PATCHES] Fw: Isn't pg_statistic a security hole - Solution Proposal
Date
Msg-id 200106121615.f5CGFNu16522@candle.pha.pa.us
Whole thread Raw
In response to Re: Re: [PATCHES] Fw: Isn't pg_statistic a security hole - Solution Proposal  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
> Tom Lane writes:
> 
> > Could we make the assumption that table names in catalogs
> > will be of type 'name'?
> 
> I wouldn't want to guarantee it for the information schema.
> 
> > If so, it'd work to make two versions of the has_table_privilege
> > function, one taking type "name" and the other taking type "text".
> > The "name" version would take its input as-is, the "text" version
> > would do case folding and truncation.
> 
> Target typing is ugly.
> 
> I've tried to look up the supposed \paraphrase{we had enough problems
> before we added the existing behaviour to setval, etc.} discussion but
> couldn't find it.  My experience on the mailing list is that it goes the
> other way.

I am confused.  What are you suggesting as far as having a name and text
version of the functions?

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


pgsql-hackers by date:

Previous
From: "Eric C. Newton"
Date:
Subject: Re: [Fwd: AW: Postgres Replication]
Next
From: Darren Johnson
Date:
Subject: PostgreSQL Replication