I've been idly amusing myself by trying to hack up support for
SQL-standard LATERAL subqueries. I've got something that turns over,
more or less:
regression=# select * from int4_tbl a, lateral (select unique1,unique2 from
tenk1 b where a.f1 = unique1) x;
f1 | unique1 | unique2
On 08/05/2012 05:58 PM, Tom Lane wrote:
I've been idly amusing myself by trying to hack up support for
SQL-standard LATERAL subqueries. I've got something that turns over,
more or less:
Awesome!!
Currently the patch only implements the syntax called out in the standard,
namely that you
I wrote:
While fooling around in the planner I realized that I have no idea what
outer-level aggregates mean in a LATERAL subquery, and neither does
Postgres:
regression=# select 1 from tenk1 a, lateral (select * from int4_tbl b where
f1 = max(a.unique1)) x;
ERROR: plan should not
Andrew Dunstan and...@dunslane.net writes:
On 08/05/2012 05:58 PM, Tom Lane wrote:
Currently the patch only implements the syntax called out in the standard,
namely that you can put LATERAL in front of a derived table, which is
to say a parenthesized sub-SELECT in FROM. It strikes me that it
Hi Robert,
From: Robert Haas [mailto:robertmh...@gmail.com]
On Thu, Aug 2, 2012 at 7:01 AM, Etsuro Fujita
fujita.ets...@lab.ntt.co.jp wrote:
The following is a comment at fileGetForeignPaths() in contrib/file_fdw.c:
/*
* If data file was sorted, and we knew it somehow, we
2012/8/6 Tom Lane t...@sss.pgh.pa.us:
Andrew Dunstan and...@dunslane.net writes:
On 08/05/2012 05:58 PM, Tom Lane wrote:
Currently the patch only implements the syntax called out in the standard,
namely that you can put LATERAL in front of a derived table, which is
to say a parenthesized
From: Bruce Momjian [mailto:br...@momjian.us]
Sent: Saturday, August 04, 2012 8:06 PM
On Sat, Aug 4, 2012 at 05:21:06PM +0300, Heikki Linnakangas wrote:
On 04.08.2012 11:01, Amit Kapila wrote:
Missed one point which needs to be handled is pg_upgrade
I don't think there's anything to do for
Hi All,
It would be helpful if someone tell me, how to verify the streaming
replication started in standby server successfully, just after the service
is started ?? Like knowing the exit code of the service started...
I know we can do it by verifying the below functions after the service is
