- 22 Mar, 2009 1 commit
-
-
Tom Lane authored
is still available, but you must now write the long equivalent --inserts or --column-inserts. This change is made to eliminate confusion with the use of -d to specify a database name in most other Postgres client programs. Original patch by Greg Mullane, modified per subsequent discussion.
-
- 04 Mar, 2009 1 commit
-
-
Peter Eisentraut authored
option. We don't want to commit to what it does, but hiding it will only cause confusion.
-
- 26 Feb, 2009 1 commit
-
-
Peter Eisentraut authored
programs that have a -W/--password option. In passing, remove the ancient PSQL_ALWAYS_GET_PASSWORDS compile option.
-
- 17 Feb, 2009 1 commit
-
-
Bruce Momjian authored
utilities. The new code allows transfer of dropped column information to the upgraded server.
-
- 07 Feb, 2009 1 commit
-
-
Bruce Momjian authored
bit more visibility to the PGOPTIONS environment variable supported by libpq. Bryce Nesbitt
-
- 05 Jan, 2009 1 commit
-
-
Tom Lane authored
performing dumps and restores in accordance with a security policy that forbids logging in directly as superuser, but instead specifies that you should log into an admin account and then SET ROLE to the superuser. In passing, clean up some ugly and mostly-broken code for quoting shell arguments in pg_dumpall. Benedek László, with some help from Tom Lane
-
- 29 Aug, 2008 1 commit
-
-
Alvaro Herrera authored
David Gould
-
- 13 Apr, 2008 1 commit
-
-
Tom Lane authored
the server version check is now always enforced. Relax the version check to allow a server that is of pg_dump's own major version but a later minor version; this is the only case that -i was at all safe to use in. pg_restore already enforced only a very weak version check, so this is really just a documentation change for it. Per discussion.
-
- 26 Mar, 2008 1 commit
-
-
Tom Lane authored
pg_dump --ignore-version comments into pg_dumpall and pg_restore pages.
-
- 20 Mar, 2008 1 commit
-
-
Tom Lane authored
dumps can be loaded into databases without the same tablespaces that the source had. The option acts by suppressing all "SET default_tablespace" commands, and also CREATE TABLESPACE commands in pg_dumpall's case. Gavin Roy, with documentation and minor fixes by me.
-
- 11 Dec, 2007 1 commit
-
-
Tom Lane authored
-
- 26 Mar, 2007 1 commit
-
-
Tom Lane authored
-
- 21 Feb, 2007 1 commit
-
-
Bruce Momjian authored
in the future.
-
- 20 Feb, 2007 1 commit
-
-
Bruce Momjian authored
environment variables. Backpatch to 8.2.X.
-
- 01 Feb, 2007 1 commit
-
-
Neil Conway authored
and --password for pg_dump, pg_dumpall and pg_restore, per complaint by Michael Schmidt. Patch from Magnus Hagander.
-
- 31 Jan, 2007 1 commit
-
-
Bruce Momjian authored
Standard English uses "may", "can", and "might" in different ways: may - permission, "You may borrow my rake." can - ability, "I can lift that log." might - possibility, "It might rain today." Unfortunately, in conversational English, their use is often mixed, as in, "You may use this variable to do X", when in fact, "can" is a better choice. Similarly, "It may crash" is better stated, "It might crash".
-
- 25 Jan, 2007 4 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
where output redirection of child processes (pg_dump) doesn't work. Dave Page
-
Bruce Momjian authored
'template1'. Dave Page
-
Bruce Momjian authored
Dave Page
-
- 15 Jan, 2007 1 commit
-
-
Neil Conway authored
roles and tablespaces, no longer users and groups. Per Dave Page. Backport to 8.2 and 8.1.
-
- 07 Oct, 2006 1 commit
-
-
Peter Eisentraut authored
portable long options. But we have had portable long options for a long time now, so this is obsolete. Now people have added options which *only* work with -X but not as regular long option, so I'm putting a stop to this: -X is deprecated; it still works, but it has been removed from the documentation, and please don't add more of them.
-
- 16 Sep, 2006 1 commit
-
-
Bruce Momjian authored
-
- 16 Jun, 2006 1 commit
-
-
Bruce Momjian authored
Backpatch documentation addition to 8.1.X.
-
- 01 Nov, 2005 1 commit
-
-
Tom Lane authored
-
- 15 Oct, 2005 1 commit
-
-
Neil Conway authored
rather than British. Patch from Michael Fuhr.
-
- 10 Oct, 2005 1 commit
-
-
Tom Lane authored
emit when given the --clean option, in favor of individual DROP ROLE commands. The old technique could not possibly work in 8.1, and was never a very good idea anyway IMHO. The DROP ROLE approach has the defect that the DROPs will fail for roles that own objects or have privileges, but perhaps we can improve that later.
-
- 25 Jul, 2005 1 commit
-
-
Tom Lane authored
I'm still working on the has_role function and information_schema changes.
-
- 21 Jun, 2005 2 commits
-
-
Tom Lane authored
using the recently added lo_create() function. The restore logic in pg_restore is greatly simplified as well, since there's no need anymore to try to adjust database references to match a new set of blob OIDs.
-
Tom Lane authored
unlike template0 and template1 does not have any special status in terms of backend functionality. However, all external utilities such as createuser and createdb now connect to "postgres" instead of template1, and the documentation is changed to encourage people to use "postgres" instead of template1 as a play area. This should fix some longstanding gotchas involving unexpected propagation of database objects by createdb (when you used template1 without understanding the implications), as well as ameliorating the problem that CREATE DATABASE is unhappy if anyone else is connected to template1. Patch by Dave Page, minor editing by Tom Lane. All per recent pghackers discussions.
-
- 29 May, 2005 1 commit
-
-
Bruce Momjian authored
-
- 06 Jan, 2005 1 commit
-
-
Tom Lane authored
discussion on pgsql-hackers-win32 list. Documentation still needs to be tweaked --- I'm not sure how to refer to the APPDATA folder in user documentation.
-
- 04 Jan, 2005 1 commit
-
-
Tom Lane authored
-
- 19 Jul, 2004 1 commit
-
-
Bruce Momjian authored
* Fix help text ordering * Add back --set-session-authorization to pg_dumpall. Updated the docs for that. Updated help for that. * Dump ALTER USER commands for the cluster owner ("pgsql"). These are dumped AFTER the create user and create database commands in case the permissions to do these have been revoked. * Dump ALTER OWNER for public schema (because it's possible to change it). This was done by adding TOC entries for the public schema, and filtering them out at archiver time. I also save the owner in the TOC entry just for the public schema. * Suppress dumping single quotes around schema_path and DateStyle options when they are set using ALTER USER or ALTER DATABASE. Added a comment to the steps in guc.c to remind people to update that list. * Fix dumping in --clean mode against a pre-7.3 server. It just sets all drop statements to assume the public schema, allowing it to restore without error. * Cleaned up text output. eg. Don't output -- Tablespaces comment if there are none. Same for groups and users. * Make the commands to DELETE FROM pg_shadow and DELETE FROM pg_group only be output when -c mode is enabled. I'm not sure why that hasn't been done before?!?! This should be good for application asap, after which I will start on regression dumping 7.0-7.4 databases. Christopher Kings-Lynne
-
- 12 Jul, 2004 1 commit
-
-
Bruce Momjian authored
pg_dump: -S, --superuser=NAME -O, --no-owner -X disable-dollar-quoting, --disable-dollar-quoting -X disable-triggers, --disable-triggers Christopher Kings-Lynne
-
- 07 Jun, 2004 1 commit
-
-
Bruce Momjian authored
-
- 29 Nov, 2003 1 commit
-
-
PostgreSQL Daemon authored
$Header: -> $PostgreSQL Changes ...
-
- 04 Nov, 2003 1 commit
-
-
Peter Eisentraut authored
-
- 02 Nov, 2003 1 commit
-
-
Peter Eisentraut authored
-
- 31 Aug, 2003 1 commit
-
-
Peter Eisentraut authored
-