- 24 9月, 2002 3 次提交
-
-
由 Peter Eisentraut 提交于
editing.
-
由 Tom Lane 提交于
backends. Given that temp tables now store data locally in the local buffer manager, these things are not going to work safely.
-
由 Tom Lane 提交于
to avoid having to write explicit casts. From Joe Conway.
-
- 23 9月, 2002 20 次提交
-
-
由 Bruce Momjian 提交于
> * Add start time to pg_stat_activity
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
The error message said so :-) In 25.3. Using PL/Python If the trigger "when" is BEFORE, you may return None or "OK" from the Python function to indicate the tuple is unmodified, "SKIP" to abort the event, or "MODIFIED" to indicate you've modified the tuple. should read If the trigger "when" is BEFORE, you may return None or "OK" from the Python function to indicate the tuple is unmodified, "SKIP" to abort the event, or "MODIFY" to indicate you've modified the tuple. elein
-
由 Bruce Momjian 提交于
up to reaching the hard limit. After opening 16(=current REST_START value) results via pg_exec, the next pg_exec tries to find an empty slot forever :-( . In PgSetResultId file pgtclId.c in the for loop there has to be done a break, if res_max ist reached. The piece of code should look like if (resid == connid->res_max) { resid = 0; break; /* the break as to be added */ } now everything works (double available results after reaching RES_START up to reaching RES_HARD_MAX) Gerhard Hintermayer
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
recent bug report). Fix processing of nailed-in-cache indexes; it appears that REINDEX DATABASE has been broken for months :-(.
-
由 Tom Lane 提交于
contains the correct statistics. This is a partial solution for the problem of allowing concurrent CREATE INDEX commands: unless they commit at nearly the same instant, the second one will see the first one's pg_class updates as committed, and won't try to update again, thus avoiding the 'tuple concurrently updated' failure.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
do.
-
由 Tom Lane 提交于
versions of bison.
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
even when dealing with a nailed-in-cache relation; otherwise, following VACUUM truncation of a system catalog, other backends might have unreasonably large values of these fields.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
YYERROR_VERBOSE" from contrib/cube and contrib/seg, and adjusts the expected output accordingly. Hopefully this will consistently pass across multiple bison versions. Joe Conway
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
columns, to allow more correct behavior in multiple-inheritance cases. Patch by Alvaro Herrera, review by Tom Lane.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
the SQL99 standard. (I'm not sure that the character-class features are quite right, but that can be fixed later.) Document SQL99 and POSIX regexps as being different features; provide variants of SUBSTRING for each.
-
- 22 9月, 2002 4 次提交
-
-
由 Tom Lane 提交于
parse analysis and into the execution code (in tablecmds.c). This eliminates a lot of unreasonably complex code that needed to have two or more execution paths in case it was dealing with a not-yet-created table column vs. an already-existing one. The execution code is always dealing with already-created tables and so needs only one case. This also eliminates some potential race conditions (the table wasn't locked between parse analysis and execution), makes it easy to fix the gripe about wrong referenced-column names generating a misleading error message, and lets us easily add a dependency from the foreign-key constraint to the unique index that it requires the referenced table to have. (Cf. complaint from Kris Jurka 12-Sep-2002 on pgsql-bugs.) Also, third try at building a deletion mechanism that is not sensitive to the order in which pg_depend entries are visited. Adding the above- mentioned dependency exposed the folly of what dependency.c had been doing: it failed for cases where B depends on C while both auto-depend on A. Dropping A should succeed in this case, but was failing if C happened to be visited before B. It appears the only solution is two separate walks over the dependency tree.
-
由 Tom Lane 提交于
-ffast-math.
-
由 Tom Lane 提交于
with OPAQUE. CREATE LANGUAGE, CREATE TRIGGER, and CREATE TYPE will all accept references to functions declared with OPAQUE --- but they will issue a NOTICE, and will modify the function entries in pg_proc to have the preferred type-safe argument or result types instead of OPAQUE. Per recent pghackers discussions.
-
由 Peter Eisentraut 提交于
-
- 21 9月, 2002 6 次提交
-
-
由 Tom Lane 提交于
Need 'isync' during TAS and 'sync' during S_UNLOCK.
-
由 Tom Lane 提交于
avoid O(N^2) behavior. Problem noted and fixed by Stephen Marshall <smarshall@wsicorp.com>, with some help from Tom Lane.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
when default expression for a domain is being used. Avoid repetitive catalog lookups.
-
由 Tom Lane 提交于
-
- 20 9月, 2002 7 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * -to_char(0,'FM999.99') returns a period, to_char(1,'FM999.99') doesn't (Karel)
-
由 Bruce Momjian 提交于
* to_char(0,'FM999.99') returns a period, to_char(1,'FM999.99') does not Karel Zak
-
由 Bruce Momjian 提交于
> I see in your recent bytea-LIKE patch > > if (datatype != BYTEAOID && pg_database_encoding_max_length() > 1) > len = pg_mbcliplen((const unsigned char *) workstr, len, len - 1); > else > len -= -1; > > Surely there's one too many minus signs in that last? Joe Conway
-
由 Bruce Momjian 提交于
fixes a few minor bugs (typos, potential buffer overruns, etc.), and fixes some spelling/grammar mistakes. Neil Conway
-
由 Bruce Momjian 提交于
Oleg Bartunov
-