> >
> >>> Since the SQL is not your fault and difficult to control, it is an
> >>> argument in favour of an optional planner mode that would perform
> >>> additional checks for redundant clauses of various kinds. The
> > default
> >>> for that would be "off" since most people don't suffer from this
> > Since the SQL is not your fault and difficult to control, it is an
> > argument in favour of an optional planner mode that would perform
> > additional checks for redundant clauses of various kinds. The
default
> > for that would be "off" since most people don't suffer from this
> > problem. B
> Subject: Re: [PERFORM] 8.3rc1 Out of memory when performing update
>
> >
> > > A simple update query, over roughly 17 million rows, populating a
> > > newly added column in a table, resulted in an out of memory error
> > > when the process memory usage reached 2GB. Could this be due to a
> > > p
> -Original Message-
> From: Andrew Sullivan [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 20, 2007 3:04 PM
> To: pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] viewing source code
>
> On Thu, Dec 20, 2007 at 01:45:08PM -0600, Roberts, Jon wrot
> -Original Message-
> From: Joshua D. Drake [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 20, 2007 1:54 PM
> To: Roberts, Jon
> Cc: 'Trevor Talbot'; Kris Jurka; Merlin Moncure; Jonah H. Harris; Bill
> Moran; pgsql-performance@postgresql.org
> Subjec
> -Original Message-
> From: Joshua D. Drake [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 20, 2007 10:40 AM
> To: Roberts, Jon
> Cc: 'Trevor Talbot'; Kris Jurka; Merlin Moncure; Jonah H. Harris; Bill
> Moran; pgsql-performance@postgresql.org
>
> -Original Message-
> From: Merlin Moncure [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 20, 2007 8:30 AM
> To: Roberts, Jon
> Cc: Alvaro Herrera; Trevor Talbot; Joshua D. Drake; Kris Jurka; Jonah H.
> Harris; Bill Moran; pgsql-performance@postgresql.org
>
views and then make
subsequent changes to pgAdmin or if the database itself needs to change to
handle this.
Jon
> -Original Message-
> From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 19, 2007 9:56 AM
> To: Roberts, Jon
> Cc: 'Trevor Talbot'
> -Original Message-
> From: Trevor Talbot [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, December 19, 2007 9:45 AM
> To: Joshua D. Drake
> Cc: Roberts, Jon; Kris Jurka; Merlin Moncure; Jonah H. Harris; Bill Moran;
> pgsql-performance@postgresql.org
> Subject: Re: [PE
-Original Message-
> From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 18, 2007 12:27 PM
> To: Roberts, Jon
> Cc: 'Kris Jurka'; Merlin Moncure; Jonah H. Harris; Bill Moran; Joshua D.
> Drake; pgsql-performance@postgresql.org
> Subject: Re: [PERFO
role.
Revoking pg_proc isn't good for users that shouldn't see other's code but
still need to be able to see their own code.
Jon
> -Original Message-
> From: Kris Jurka [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 17, 2007 10:51 PM
> To: Merlin Moncure
it isn't a feature today, what table has the source code in it? Maybe I
can revoke that.
Jon
> -Original Message-
> From: Jonah H. Harris [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 14, 2007 3:04 PM
> To: Bill Moran
> Cc: Joshua D. Drake; Roberts, Jon; pg
7 3:04 PM
> To: Bill Moran
> Cc: Joshua D. Drake; Roberts, Jon; pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] viewing source code
>
> On Dec 14, 2007 2:03 PM, Bill Moran <[EMAIL PROTECTED]>
> wrote:
> > I disagree here. If they're connecting remotely
> > In an ideal world, if a user can't modify a function, he/she shouldn't
> be
> > able to see the source code. If the user can execute the function, then
> the
> > user should be able to see the signature of the function but not the
> body.
>
> I doubt that's going to happen. Mainly because I
Is it possible yet in PostgreSQL to hide the source code of functions from
users based on role membership? I would like to avoid converting the code
to C to secure the source code and I don't want it obfuscated either.
In an ideal world, if a user can't modify a function, he/she shouldn't be
ab
15 matches
Mail list logo
