http://www.postgresql.org/docs/8.4/static/storage-page-layout.html
I fail to find the size of the *row* header on that link.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
What is the width (in bytes) of the meta data associated with each row
in postgresql?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
> What do you mean by resursive queries? A query can have a subquery
> which calls a function which executes another query. That counts as
> recursion in my book. What type of recursion are you thinking of?
No, recursion is a pretty well defined term. See
http://en.wikipedia.org/wiki/Recursion
S
> I don't think anybody has written the syntactic sugar, but someone did
> write a function that provides equivalent output.
I think it is important that the funcionality lies in the database
engine itself: In that way it can more efficiently make use of the
optimizer.
Also, I think this "recursi
Are there any plans on implementing support for recursive queries in
postgresql in the near future? If so: When?
I can see there has been some discussion on the subject in the
developer-group for quite some time ago, but aparently all thoughts of
recursive queries has been stalled. :-(
Regards
-
I have the following problem:
1) I have one master table with a primary key.
2) In addition I have *several* slave tables, all refering to a primary
key in the master table (no two slave tables refer to the same master key)
I wan't to make sure that no keys in the master table are unreferred, th
> To ease any pain, what about a configuration setting for the build
> script for postgres (and psql) which changes the default behaviour for
> the AUTOCOMMIT setting.
I really agree on the need for a posibility to set autocommit = off
*regardless* of the client:
On a system using both psql, php
