Hello,
I am writing a blog on backups with postgresql, which I plan at some
point (if someone doesn't beat me to it) on turning into a patch for the
docs but I found this inconsistency:
The docs state that:
In particular, it must have read access to all tables that you want to
back up, so in
On fre, 2010-07-23 at 11:48 -0700, Joshua D. Drake wrote:
In particular, it must have read access to all tables that you want
to
back up, so in practice you almost always have to run it as a database
superuser.
Ignoring the fact that databases have a lot more objects than tables,
there is
On Fri, 2010-07-23 at 21:55 +0300, Peter Eisentraut wrote:
On fre, 2010-07-23 at 11:48 -0700, Joshua D. Drake wrote:
In particular, it must have read access to all tables that you want
to
back up, so in practice you almost always have to run it as a database
superuser.
Ignoring the
On Monday 20 April 2009 01:35:25 Robert Grabowski wrote:
I found some inconsistency on WITH keyword:
Yes, there are lots of those. Deal with it. ;-)
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Hi,
I found some inconsistency on WITH keyword:
1) = \h CREATE TABLE
[...]
[ WITH ( storage_parameter [= value] [, ... ] ) ]
[...]
= is required
2) = \h CREATE ROLE
Command: CREATE ROLE
Description: define a new database role
Syntax:
CREATE ROLE name [ [ WITH ] option [ ... ] ]
How that debug_print_parse outputs as LOG instead of DEBUG in 8.4,
should it be log_print_parse?
--
Bruce Momjian br...@momjian.ushttp://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Bruce Momjian br...@momjian.us writes:
How that debug_print_parse outputs as LOG instead of DEBUG in 8.4,
should it be log_print_parse?
No, it's still a debugging tool.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
