| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
This was for demonstration only, and now it was creating compiler
warnings from zlib without an obvious fix (see also
d923125b77c5d698bb8107a533a21627582baa43), let's just remove it. The
"directory" format is presumably similar enough anyway.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gzFile is already a pointer, so code like
gzFile *handle = gzopen(...)
is wrong.
This used to pass silently because gzFile used to be defined as void*,
and you can assign a void* to a void**. But somewhere between zlib
versions 1.2.3.4 and 1.2.6, the definition of gzFile was changed to
struct gzFile_s *, and with that new definition this usage causes
compiler warnings.
So remove all those extra pointer decorations.
There is a related issue in pg_backup_archiver.h, where
FILE *FH; /* General purpose file handle */
is used throughout pg_dump as sometimes a real FILE* and sometimes a
gzFile handle, which also causes warnings now. This is not yet fixed
here, because it might need more code restructuring.
|
|
|
|
| |
Per recent discussions on pgsql-hackers regarding parallel pg_dump.
|
|
|
|
| |
pg_dumpall to use the same memory allocation functions as the others.
|
|
|
|
|
| |
with its original functions. The previous function migration would
cause too many difficulties in back-patching.
|
|
|
|
| |
ignoring errors and call-site error checking.
|
|
|
|
|
|
| |
This addresses only those cases that are easy to fix by adding or
moving a const qualifier or removing an unnecessary cast. There are
many more complicated cases remaining.
|
| |
|
|
|
|
|
|
| |
In passing, make invocations of lo_xxx functions a bit more schema-safe.
Itagaki Takahiro
|
|
|
|
|
|
|
|
| |
post-data step is run in a separate worker child (a thread on Windows, a child
process elsewhere) up to the concurrent number specified by the new pg_restore
command-line --multi-thread | -m switch.
Andrew Dunstan, with some editing by Tom Lane.
|
|
|
|
|
|
| |
errno string when complaining of fopen failures. Per gripe from Bob
Pawley, it's not always instantly obvious to the user which name we
tried to open.
|
|
|
|
| |
Per report and partial patch from Chad Wagner.
|
|
|
|
| |
are initialized with a string literal. Patch from Stefan Huehner.
|
|
|
|
| |
binary dump formats.
|
|
|
|
|
|
|
| |
where possible, and fix some sites that apparently thought that fgets()
will overwrite the buffer by one byte.
Also add some strlcpy() to eliminate some weird memory handling.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
object types, rather than by OID. This should help ensure consistent
dump output from databases that are logically the same but have different
histories, per recent discussion about 'diffing' databases. The patch
is bulky because of renaming of fields, but not very complicated.
Also, do some tweaking to cause BLOB restoration to be done in a better
order, and clean up pg_restore's textual output to exactly match pg_dump.
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Fix pg_restore tar log output bug where Special flag wasn't being
initialized; bug seen on XP.
|
|
|
|
| |
sizes.
|
| |
|
| |
|
| |
|
|
|
|
| |
Use off_t and size_t in pg_dump to handle file offset arithmetic correctly.
|
|
|
|
| |
that would do the wrong thing with BLOB OIDs exceeding 2G.
|
|
|
|
| |
Mario Weilguni
|
|
|
|
| |
tests pass.
|
|
|
|
| |
in messages and documentation.
|
|
|
|
|
|
| |
--verbose messages, which had not been considered so far. Output to the
terminal should okay now; comments written into the dump are still English
only, which may or may not be the desirable thing.
|
|
|
|
| |
message clean up.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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).
|
| |
|
| |
|
|
|
|
|
|
|
| |
- 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"'
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
- Fix handling of --tables=* (multiple tables never worked properly, AFAICT)
- strdup() the current user in DB routines
- Check results of IO routines more carefully.
- Check results of PQ routines more carefully.
Have not fixed index output yet.
|
|
|
|
|
|
| |
BLOB_BATCH_SIZE)
Prevent dumping of languages from template1.
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
|
|
|
|
| |
- The problems Jan reported
- incompatibility with configure (now uses HAVE_LIBZ instead of HAVE_ZLIB)
- a problem in auto-detecting archive file format on piped archives
Philip Warner
|
|
|