- 01 Aug, 2006 1 commit
-
-
Bruce Momjian authored
and -N options to exclude objects. Also support regular expressions for option object names. Greg Sabino Mullane
-
- 27 Jul, 2006 1 commit
-
-
Tom Lane authored
the opportunity to treat COUNT(*) as a zero-argument aggregate instead of the old hack that equated it to COUNT(1); this is materially cleaner (no more weird ANYOID cases) and ought to be at least a tiny bit faster. Original patch by Sergey Koposov; review, documentation, simple regression tests, pg_dump and psql support by moi.
-
- 14 Jul, 2006 1 commit
-
-
Bruce Momjian authored
-
- 11 Jul, 2006 1 commit
-
-
Bruce Momjian authored
-
- 02 Jul, 2006 1 commit
-
-
Bruce Momjian authored
ITAGAKI Takahiro
-
- 09 Jun, 2006 1 commit
-
-
Tom Lane authored
was invoking obj_description() for each large object chunk, instead of once per large object. This code is new as of 8.1, which may explain why the problem hadn't been noticed already.
-
- 07 Jun, 2006 1 commit
-
-
Bruce Momjian authored
o remove many WIN32_CLIENT_ONLY defines o add WIN32_ONLY_COMPILER define o add 3rd argument to open() for portability o add include/port/win32_msvc directory for system includes Magnus Hagander
-
- 28 May, 2006 2 commits
-
-
Tom Lane authored
and standard_conforming_strings; likewise for the other client programs that need it. As per previous discussion, a pg_dump dump now conforms to the standard_conforming_strings setting of the source database. We don't use E'' syntax in the dump, thereby improving portability of the SQL. I added a SET escape_strings_warning = off command to keep the dumps from getting a lot of back-chatter from that.
-
Alvaro Herrera authored
Per Coverity bug #304. Thanks to Martijn van Oosterhout for reporting it. Zero out the pointer fields of PGresult so that these mistakes are more easily catched, per discussion.
-
- 26 May, 2006 1 commit
-
-
Bruce Momjian authored
'off'. This allows pg_dump output with standard_conforming_strings = 'on' to generate proper strings that can be loaded into other databases without the backslash doubling we typically do. I have added the dumping of the standard_conforming_strings value to pg_dump. I also added standard backslash handling for plpgsql.
-
- 05 Mar, 2006 1 commit
-
-
Bruce Momjian authored
-
- 03 Mar, 2006 1 commit
-
-
Tom Lane authored
instead of the old deprecated ones. Volkan Yazici, with some editorializing by moi.
-
- 02 Mar, 2006 1 commit
-
-
Tom Lane authored
make use of the recently added ability to create a shell type explicitly. I also put in place some infrastructure to allow dump/no dump decisions to be made separately for each database object, rather than the former hardwired 'dump if in a dumpable schema' policy. This was needed anyway for shell types so now seemed a convenient time to do it. The flexibility isn't exposed to the user yet, but is ready for future extensions.
-
- 21 Feb, 2006 1 commit
-
-
Tom Lane authored
by decompiling the typdefaultbin expression, not just printing the typdefault text which may be out-of-date or assume the wrong schema search path. (It's the same hazard as for adbin vs adsrc in column defaults.) The catalogs.sgml spec for pg_type implies that the correct procedure is to look to typdefaultbin first and consider typdefault only if typdefaultbin is NULL. I made dumping of both domains and base types do that, even though in the current backend code typdefaultbin is always correct for domains and typdefault for base types --- might as well try to future-proof it a little. Per bug report from Alexander Galler.
-
- 12 Feb, 2006 2 commits
-
-
Bruce Momjian authored
Hiroshi Saito
-
Bruce Momjian authored
comments on cluster global objects like databases, tablespaces, and roles. It touches a lot of places, but not much in the way of big changes. The only design decision I made was to duplicate the query and manipulation functions rather than to try and have them handle both shared and local comments. I believe this is simpler for the code and not an issue for callers because they know what type of object they are dealing with. This has resulted in a shobj_description function analagous to obj_description and backend functions [Create/Delete]SharedComments mirroring the existing [Create/Delete]Comments functions. pg_shdescription.h goes into src/include/catalog/ Kris Jurka
-
- 21 Jan, 2006 1 commit
-
-
Bruce Momjian authored
Continue to support GRANT ON [TABLE] for sequences for backward compatibility; issue warning for invalid sequence permissions. [Backward compatibility warning message.] Add USAGE permission for sequences that allows only currval() and nextval(), not setval(). Mention object name in grant/revoke warnings because of possible multi-object operations.
-
- 09 Jan, 2006 1 commit
-
-
Tom Lane authored
operator names. This is needed when dumping operator definitions that have COMMUTATOR (or similar) links to operators in other schemas. Apparently Daniel Whitter is the first person ever to try this :-(
-
- 06 Jan, 2006 1 commit
-
-
Bruce Momjian authored
-
- 03 Dec, 2005 1 commit
-
-
Tom Lane authored
than owned by nobody. This results in cleaner display of language ACLs, since the backend's aclchk.c uses the same convention. AFAICS there is no practical difference but it's nice to avoid emitting SET SESSION AUTHORIZATION; also this will make it easier to transition pg_dump to some future version in which we may include an explicit ownership column in pg_language. Per gripe from David Begley.
-
- 22 Nov, 2005 1 commit
-
-
Bruce Momjian authored
comment line where output as too long, and update typedefs for /lib directory. Also fix case where identifiers were used as variable names in the backend, but as typedefs in ecpg (favor the backend for indenting). Backpatch to 8.1.X.
-
- 15 Oct, 2005 1 commit
-
-
Bruce Momjian authored
-
- 21 Sep, 2005 1 commit
-
-
Tom Lane authored
given, per gripe from Michael Fuhr.
-
- 05 Sep, 2005 1 commit
-
-
Tom Lane authored
as per my recent proposal. For now the template data is hard-wired in proclang.c --- this should be replaced later by a new shared system catalog, but we don't want to force initdb during 8.1 beta. This change lets us cleanly load existing dump files even if they contain outright wrong information about a PL's support functions, such as a wrong path to the shared library or a missing validator function. Also, we can revert the recent kluges to make pg_dump dump PL support functions that are stored in pg_catalog. While at it, I removed the code in pg_regress that replaced $libdir with a hardcoded path for temporary installations. This is no longer needed given our support for relocatable installations.
-
- 23 Aug, 2005 1 commit
-
-
Tom Lane authored
use these instead of its previous hack of changing pg_class.reltriggers. Documentation is lacking, will add that later. Patch by Satoshi Nagayasu, review and some extra work by Tom Lane.
-
- 15 Aug, 2005 2 commits
- 12 Aug, 2005 1 commit
-
-
Tom Lane authored
whenever we generate a new OID. This prevents occasional duplicate-OID errors that can otherwise occur once the OID counter has wrapped around. Duplicate relfilenode values are also checked for when creating new physical files. Per my recent proposal.
-
- 10 Jul, 2005 2 commits
-
-
Bruce Momjian authored
The Problem: Occassionally a DBA needs to dump a database to a new encoding. In instances where the current encoding, (or lack of an encoding, like SQL_ASCII) is poorly supported on the target database server, it can be useful to dump into a particular encoding. But, currently the only way to set the encoding of a pg_dump file is to change client_encoding in postgresql.conf and restart postmaster. This is more than a little awkward for production systems. Magnus Hagander
-
Bruce Momjian authored
into pg_catalog rather than public, and supports dumping languages whose handlers are found there. This will make it easier to drop the public schema if desired. Unlike the previous patch, the comments have been updated and I have reformatted some code to meet Alvarro's request to stick to 80 cols. (I actually aghree with this - it makes printing the code much nicer). I think I did the right thing w.r.t versions earlier than 7.3, but I have no real way of checking, so that should be checked by someone with more/older knowledge than me ;-) Andrew Dunstan
-
- 02 Jul, 2005 1 commit
-
-
Bruce Momjian authored
Improve code clarity by using macros for E'' processing.
-
- 01 Jul, 2005 1 commit
-
-
Bruce Momjian authored
files.
-
- 30 Jun, 2005 1 commit
-
-
Tom Lane authored
-
- 21 Jun, 2005 1 commit
-
-
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.
-
- 07 Jun, 2005 1 commit
-
-
Tom Lane authored
not schema-safe. Per report from Jochem van Dieten.
-
- 30 Apr, 2005 1 commit
-
-
Neil Conway authored
a warning when a variable is used as a format string for printf() and similar functions (if the variable is derived from untrusted data, it could include unexpected formatting sequences). This emits too many warnings to be enabled by default, but it does flag a few dubious constructs in the Postgres tree. This patch fixes up the obvious variants: functions that are passed a variable format string but no additional arguments. Most of these are harmless (e.g. the ruleutils stuff), but there is at least one actual bug here: if you create a trigger named "%sfoo", pg_dump will read uninitialized memory and fail to dump the trigger correctly.
-
- 15 Apr, 2005 1 commit
-
-
Tom Lane authored
which induced bug #1597 in addition to having several other misbehaviors (like labeling the dump with a completion time having nothing to do with reality). Instead just print out the desired strings where RestoreArchive was already emitting the 'PostgreSQL database dump' and 'PostgreSQL database dump complete' strings.
-
- 12 Apr, 2005 1 commit
-
-
Tom Lane authored
be supported for all datatypes. Add CREATE AGGREGATE and pg_dump support too. Add specialized min/max aggregates for bpchar, instead of depending on text's min/max, because otherwise the possible use of bpchar indexes cannot be recognized. initdb forced because of catalog changes.
-
- 01 Apr, 2005 1 commit
-
-
Tom Lane authored
-
- 14 Mar, 2005 1 commit
-
-
Tom Lane authored
if it finds a pg_rewrite entry for which there is no pg_class entry. Per report from Andrew Slobodyanyk.
-