summaryrefslogtreecommitdiff
path: root/src/bin/pg_dump/pg_backup.h
Commit message (Collapse)AuthorAgeFilesLines
* Please find attached a small patch so that "pg_restore" ignores some sqlBruce Momjian2004-04-221-1/+6
| | | | | | | | errors. This is the second submission, which integrates Tom comments about localisation and exit code. I also added some comments about one sql command which is not ignored. Fabien COELHO
* Use the new GUC variable default_with_oids in pg_dump, rather than usingBruce Momjian2004-03-241-2/+2
| | | | | | | | | WITH/WITHOUT OIDS in dump files. This makes dump files more portable. I have updated the pg_dump version so old binary dumps will load fine. Pre-7.5 dumps use WITHOUT OIDS in SQL were needed, so they should be fine.
* Massive overhaul of pg_dump: make use of dependency information fromTom Lane2003-12-061-21/+17
| | | | | | | pg_depend to determine a safe dump order. Defaults and check constraints can be emitted either as part of a table or domain definition, or separately if that's needed to break a dependency loop. Lots of old half-baked code for controlling dump order removed.
* $Header: -> $PostgreSQL Changes ...PostgreSQL Daemon2003-11-291-1/+1
|
* pg_dump/pg_restore now always use SET SESSION AUTHORIZATION, not \connect,Tom Lane2003-09-231-7/+2
| | | | | | | to control object ownership. The use-set-session-authorization and no-reconnect switches are obsolete (still accepted on the command line, but they don't do anything). This is a precursor to fixing handling of CREATE SCHEMA, which will be a separate commit.
* pg_dump and pg_restore -r had managed to diverge on the ordering ofTom Lane2003-08-281-3/+4
| | | | | different object types. Fix, and centralize logic to try to prevent the same mistake in future.
* pgindent run.Bruce Momjian2002-09-041-8/+9
|
* Reimplement pg_dumpall in C. Currently no change in functionality,Peter Eisentraut2002-08-271-6/+1
| | | | except that it's more robust, reconnects less often, and is NLS'ed.
* Enable large file support.Peter Eisentraut2002-08-201-2/+2
| | | | Use off_t and size_t in pg_dump to handle file offset arithmetic correctly.
* Make pg_dump output more portable and more pleasing to look at.Peter Eisentraut2002-08-181-2/+5
| | | | | | | | | | | | | | | | | The -n and -N options were removed. Quoting is now smart enough to supply quotes if and only if necessary. Numerical types are now printed without quotes, except in cases of special values such as NaN. Boolean values printed as true and false. Most string literals now do not escape whitespace characters (newlines, etc.) for portability. SET SESSION AUTHORIZATION argument is a string literal, to follow SQL. Made commands output by pg_dump use consistent spacing and indentation.
* More clearly document in pg_dump when we are dealing with an object nameBruce Momjian2002-07-041-2/+2
| | | | as it appears in the schema dump, and index tags.
* First pass at schema-fying pg_dump/pg_restore. Much to do still,Tom Lane2002-05-101-25/+8
| | | | but the basic capability seems to work.
* Be more wary about mixed-case database names and user names. GetTom Lane2002-02-111-4/+5
| | | | the CREATE DATABASE command right in pg_dump -C case.
* Another pgindent run. Fixes enum indenting, and improves #endifBruce Momjian2001-10-281-6/+7
| | | | spacing. Also adds space for one-line comments.
* pgindent run on all C files. Java run to follow. initdb/regressionBruce Momjian2001-10-251-17/+20
| | | | tests pass.
* Consistently use gcc's __attribute__((format)) to check sprintf-styleTom Lane2001-10-031-3/+6
| | | | | format strings wherever possible. Remarkably, this exercise didn't turn up any inconsistencies, but it seems a good idea for the future.
* Add option to output SET SESSION AUTHORIZATION commands rather thanPeter Eisentraut2001-08-221-1/+2
| | | | | \connect, to avoid possible password prompts and such, at the drawback of having to have superuser access.
* National language support for pg_dump and pg_restore. Combined with bigPeter Eisentraut2001-06-271-2/+2
| | | | message clean up.
* Add -U and -W options to pg_dump and friends to support non-interactivePeter Eisentraut2001-05-171-1/+6
| | | | | specification of username (like in psql). pg_dumpall now works with password authentication.
* - Fixed CONSTRAINT TRIGGER dump to record tgconstrelid properlyPhilip Warner2001-04-251-2/+9
| | | | - pgsql v7.0 compatbility
* Patch to put rudimentary dependency support into pg_dump. This addressesPhilip Warner2001-04-011-4/+8
| | | | | | | | | | | | the UDT/function order problem. - Rudimentary support for dependencies in archives. Uses dependencies to modify the OID used in sorting TOC entries. This will NOT handle multi-level dependencies, but will manage simple relationships like UDTs & their functions. - Treat OIDs with more respect (avoid using ints, use macros for conversion & comparison).
* pgindent run. Make it all clean.Bruce Momjian2001-03-221-65/+67
|
* - Added CVS headers to filesPhilip Warner2001-03-191-0/+1
| | | | | | | - Avoid forcing table name to lower case in FixupBlobXrefs - Removed fmtId calls for all ArchiveEntry name fields. This fixes quoting problems in trigger enable/disable code for mixed case table names, and avoids commands like 'pg_restore -t '"TblA"'
* Restructure the key include files per recent pghackers discussion: thereTom Lane2001-02-101-5/+2
| | | | | | | | | | | are now separate files "postgres.h" and "postgres_fe.h", which are meant to be the primary include files for backend .c files and frontend .c files respectively. By default, only include files meant for frontend use are installed into the installation include directory. There is a new make target 'make install-all-headers' that adds the whole content of the src/include tree to the installed fileset, for use by people who want to develop server-side code without keeping the complete source tree on hand. Cleaned up a whole lot of crufty and inconsistent header inclusions.
* Remove -k unix socketpath option from client side, allow hostname withBruce Momjian2000-11-131-3/+1
| | | | leading slash to behave as a unix socket path.
* UUNET is looking into offering PostgreSQL as a part of a managed webBruce Momjian2000-11-131-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | hosting product, on both shared and dedicated machines. We currently offer Oracle and MySQL, and it would be a nice middle-ground. However, as shipped, PostgreSQL lacks the following features we need that MySQL has: 1. The ability to listen only on a particular IP address. Each hosting customer has their own IP address, on which all of their servers (http, ftp, real media, etc.) run. 2. The ability to place the Unix-domain socket in a mode 700 directory. This allows us to automatically create an empty database, with an empty DBA password, for new or upgrading customers without having to interactively set a DBA password and communicate it to (or from) the customer. This in turn cuts down our install and upgrade times. 3. The ability to connect to the Unix-domain socket from within a change-rooted environment. We run CGI programs chrooted to the user's home directory, which is another reason why we need to be able to specify where the Unix-domain socket is, instead of /tmp. 4. The ability to, if run as root, open a pid file in /var/run as root, and then setuid to the desired user. (mysqld -u can almost do this; I had to patch it, too). The patch below fixes problem 1-3. I plan to address #4, also, but haven't done so yet. These diffs are big enough that they should give the PG development team something to think about in the meantime :-) Also, I'm about to leave for 2 weeks' vacation, so I thought I'd get out what I have, which works (for the problems it tackles), now. With these changes, we can set up and run PostgreSQL with scripts the same way we can with apache or proftpd or mysql. In summary, this patch makes the following enhancements: 1. Adds an environment variable PGUNIXSOCKET, analogous to MYSQL_UNIX_PORT, and command line options -k --unix-socket to the relevant programs. 2. Adds a -h option to postmaster to set the hostname or IP address to listen on instead of the default INADDR_ANY. 3. Extends some library interfaces to support the above. 4. Fixes a few memory leaks in PQconnectdb(). The default behavior is unchanged from stock 7.0.2; if you don't use any of these new features, they don't change the operation. David J. MacKenzie
* - Added --create, --no-owner, --superuser, --no-reconnect (pg_dump & pg_restore)Philip Warner2000-08-011-3/+23
| | | | | | | | | | | | - Added code to dump 'Create Schema' statement (pg_dump) - Don't bother to disable/enable triggers if we don't have a superuser (pg_restore) - Cleaned up code for reconnecting to database. - Force a reconnect as superuser before enabling/disabling triggers. - Added & Removed --throttle (pg_dump) - Fixed minor bug in language dumping code: expbuffres were not being reset. - Fixed version number initialization in _allocAH (pg_backup_archiver.c) - Added second connection when restoring BLOBs to allow temp. table to survive (db reconnection causes temp tables to be lost).
* Some pedantic compile syntax errors to fix with the following patchBruce Momjian2000-07-271-2/+4
| | | | | | for today's snapshot Andreas
* - Support for BLOB output from pg_dump and input via pg_restorePhilip Warner2000-07-211-125/+154
| | | | | | | - Support for direct DB connection in pg_restore - Fixes in support for --insert flag - pg_dump now outputs in modified OID order - various other bug fixes
* pg_dump patch from Philip WarnerBruce Momjian2000-07-041-0/+125
View Lorry Controller Status