Re: [GENERAL] WAL's listing in pg_xlog by some sql query

On Sat, Jun 4, 2016 at 11:34 PM, Vik Fearing wrote: > On 03/06/16 04:32, Michael Paquier wrote: >> pg_ls_dir() has a check on superuser() embedded in its code. > > So what? That's what SECURITY DEFINER is all about. Yes you are right. I missed completely the point :) Thanks

Re: [GENERAL] RowDescription via the SQL?

2016-06-03 1:55 GMT+03:00 Merlin Moncure : > On Thu, Jun 2, 2016 at 1:14 AM, Dmitry Igrishin wrote: >> Hi, >> >> It's possible to query pg_prepared_statements view to obtain the >> information about >> parameters used in the statement that was prepared. But

Re: [GENERAL] How SQL SELECT * statement works in Postgres?

On Sunday, June 5, 2016, Sachin Srivastava wrote: > Dear Team, > > Kindly inform to me How PostgreSQL Processes SQL Statements internally? > > How SQL SELECT * statement works in Postgres? >

Re: [GENERAL] How SQL SELECT * statement works in Postgres?

Sachin Srivastava schrieb am 05.06.2016 um 11:16: Kindly inform to me How PostgreSQL Processes SQL Statements internally? How SQL SELECT * statement works in Postgres? Check out Bruce's presentations:

Re: [GENERAL] How SQL SELECT * statement works in Postgres?

On 06/05/2016 11:16 AM, Sachin Srivastava wrote: Dear Team, Kindly inform to me How PostgreSQL Processes SQL Statements internally? How SQL SELECT * statement works in Postgres? I guess this is a good

[GENERAL] How SQL SELECT * statement works in Postgres?

Dear Team, Kindly inform to me How PostgreSQL Processes SQL Statements internally? How SQL SELECT * statement works in Postgres? Regards, SSR