- 28 May, 2002 1 commit
-
-
Tom Lane authored
having names conflicting with system objects will work --- the search path is now user-schema, pg_catalog rather than implicitly the other way around. Note this requires being careful to explicitly qualify references to system names whenever pg_catalog is not first in the search path. Also, add support for dumping ACLs of schemas.
-
- 22 May, 2002 1 commit
-
-
Peter Eisentraut authored
function body (and other properties) as a function in the language is created. This generalizes ad hoc code that already existed for the built-in languages. The validation now happens after the pg_proc tuple of the new function is created, so it is possible to define recursive SQL functions. Add some regression test cases that cover bogus function definition attempts.
-
- 19 May, 2002 1 commit
-
-
Peter Eisentraut authored
-
- 18 May, 2002 1 commit
-
-
Peter Eisentraut authored
I took the opportunity to remove the pg_proc.proistrusted field.
-
- 17 May, 2002 1 commit
-
-
Peter Eisentraut authored
-
- 13 May, 2002 1 commit
-
-
Tom Lane authored
underlying function; but cause psql's \do to show the underlying function's comment if the operator has no comment of its own, to preserve the useful functionality of the original behavior. Also, implement COMMENT ON SCHEMA. Patch from Rod Taylor.
-
- 10 May, 2002 1 commit
-
-
Tom Lane authored
but the basic capability seems to work.
-
- 06 May, 2002 1 commit
-
-
Tom Lane authored
some of his own privileges.
-
- 29 Apr, 2002 2 commits
- 24 Apr, 2002 4 commits
-
-
Peter Eisentraut authored
any size now.
-
Bruce Momjian authored
unused function arguments, and makes the TableInfo struct slightly smaller by removing an unnecessary member. Neil Conway <neilconway@rogers.com>
-
Bruce Momjian authored
Apparently, you need to make two calls to appendPQExpBuffer() to use fmtId() twice, because it uses a static buffer (thanks for spotting this Tom). Another revision of the patch is attached. Neil Conway <neilconway@rogers.com>
-
Bruce Momjian authored
Appears I forgot to update the docs earlier. Rod Taylor
-
- 21 Apr, 2002 1 commit
-
-
Peter Eisentraut authored
-
- 19 Apr, 2002 1 commit
-
-
Tom Lane authored
_RETURN now, since there's no need to keep 'em unique anymore.
-
- 18 Apr, 2002 1 commit
-
-
Tom Lane authored
DROP RULE and COMMENT ON RULE syntax adds an 'ON tablename' clause, similar to TRIGGER syntaxes. To allow loading of existing pg_dump files containing COMMENT ON RULE, the COMMENT code will still accept the old syntax --- but only if the target rulename is unique across the whole database.
-
- 13 Apr, 2002 1 commit
-
-
Bruce Momjian authored
some old code to add PK constraints to CREATE TABLE. That stuff had been removed as part of my original patch for pg_dump a little while ago. The attached patch fixes this by removing (again :-) ) the code in dumpTables() to perform PK creation during CREATE TABLE. I briefly tested it locally and it fixes both of Tom's test cases. Please apply. Cheers, Neil -- Neil Conway <neilconway@rogers.com>
-
- 11 Apr, 2002 1 commit
-
-
Tom Lane authored
entries, per pghackers discussion. This fixes aggregates to live in namespaces, and also simplifies/speeds up lookup in parse_func.c. Also, add a 'proimplicit' flag to pg_proc that controls whether a type coercion function may be invoked implicitly, or only explicitly. The current settings of these flags are more permissive than I would like, but we will need to debate and refine the behavior; for now, I avoided breaking regression tests as much as I could.
-
- 05 Apr, 2002 2 commits
-
-
Bruce Momjian authored
Rod Taylor
-
Tom Lane authored
volatile), rather than the old cachable/noncachable distinction. This allows indexscan optimizations in many places where we formerly didn't. Also, add a pronamespace column to pg_proc (it doesn't do anything yet, however).
-
- 21 Mar, 2002 1 commit
-
-
Bruce Momjian authored
-
- 06 Mar, 2002 1 commit
-
-
Bruce Momjian authored
so index is not on table during COPY. > > AFAICT, the patch I posted to -patches a little while to enable the > > usage of ALTER TABLE ADD PRIMARY KEY by pg_dump hasn't been applied, nor > > is it in the unapplied patches list. I was under the impression that > > this was in the queue for application -- did it just get lost? Neil Conway <neilconway@rogers.com>
-
- 27 Feb, 2002 1 commit
-
-
Tom Lane authored
matches the sequence name from pg_class. This fails if the sequence has been renamed, and seems rather pointless in any case. Also improve a couple of error messages about inconsistencies.
-
- 11 Feb, 2002 1 commit
-
-
Tom Lane authored
the CREATE DATABASE command right in pg_dump -C case.
-
- 06 Feb, 2002 1 commit
-
-
Tom Lane authored
-
- 25 Jan, 2002 1 commit
-
-
Tom Lane authored
the individual privilege bits. I regard this as an important change for cross-version compatibility: without this, a 7.1 dump loaded into 7.2 is likely to be short a few privileges.
-
- 18 Jan, 2002 1 commit
-
-
Bruce Momjian authored
tom lane
-
- 11 Jan, 2002 1 commit
-
-
Tom Lane authored
their names from pg_class. This considerably reduces the window wherein someone could DROP or ALTER a table that pg_dump is intending to dump. Not a perfect solution, but definitely an improvement. Per complaints from Marc Fournier; patch by Brent Verner with some kibitzing by Tom Lane.
-
- 28 Oct, 2001 1 commit
-
-
Bruce Momjian authored
spacing. Also adds space for one-line comments.
-
- 25 Oct, 2001 1 commit
-
-
Bruce Momjian authored
tests pass.
-
- 22 Oct, 2001 1 commit
-
-
Tom Lane authored
-
- 03 Oct, 2001 2 commits
-
-
Tom Lane authored
'aggname (aggtype)'. The old syntax 'aggname aggtype' is still accepted for backwards compatibility. Fix pg_dump, which was actually broken for most cases of user-defined aggregates. Clean up error messages associated with these commands.
-
Thomas G. Lockhart authored
-
- 01 Oct, 2001 1 commit
-
-
Tom Lane authored
pg_get_indexdef() function, rather than reaching into the system catalogs for itself. This eliminates a fair amount of redundant code. Also, since I just changed pg_get_indexdef() to suppress display of default index opclasses, this will mean that 7.2 and later dumps will not mention opclasses unless they are non-default opclasses. Should make life easier for future index opclass reorganizations.
-
- 21 Sep, 2001 1 commit
-
-
Peter Eisentraut authored
in messages and documentation.
-
- 07 Sep, 2001 1 commit
-
-
Tom Lane authored
coercing OID literals to OID in its queries. Depending on the query and the server version, this could cause failures for OIDs over 2 billion.
-
- 06 Sep, 2001 1 commit
-
-
Tom Lane authored
If there's anyone out there who's actually using datatype-defined default values, this will be an incompatible change in behavior ... but the old behavior was so broken that I doubt anyone was using it.
-
- 27 Aug, 2001 2 commits