Re: [HACKERS] Recursive queries? - Mailing list pgsql-hackers

From Vadim B. Mikheev
Subject Re: [HACKERS] Recursive queries?
Date
Msg-id 34ED53F5.B3F6CEE9@sable.krasnoyarsk.su
Whole thread Raw
In response to Recursive queries?  (Michael Meskes <meskes@topsystem.de>)
List pgsql-hackers
Michael Meskes wrote:
>
> I know that postgres originally was able to do recursive queries like
>
> retrieve* into a from a ...
>
> Is this still possible with PostgreSQL? If so, is it just for one statement
> or even as a block?

Yes, it's possible. This is from spi.txt:
---
                         Data changes visibility

   PostgreSQL data changes visibility rule: during a query execution, data
changes made by the query itself (via SQL-function, SPI-function, triggers)
are invisible to the query scan.  For example, in query

   INSERT INTO a SELECT * FROM a

   tuples inserted are invisible for SELECT' scan.  In effect, this
duplicates the database table within itself (subject to unique index
rules, of course) without recursing.

   Changes made by query Q are visible by queries which are started after
query Q, no matter whether they are started inside Q (during the execution
of Q) or after Q is done.
---

Second query 'INSERT INTO a SELECT * FROM a' inside BEGIN/END
will see tuples inserted by first one. Pg uses special CommandCounter
to distinguish changes made in the same transaction.

> This happens to be the area I worked on for several years.

I also like such areas :)

Vadim

pgsql-hackers by date:

Previous
From: Ronald Baljeu
Date:
Subject: Re: [HACKERS] Solution to the pg_user passwd problem !?? (c)
Next
From: "Meskes, Michael"
Date:
Subject: RE: [HACKERS] Recursive queries?