aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Remove useless O_DIROPEN stuff.Peter Eisentraut2002-09-24
|
* Tweak conversion names to follow the established naming scheme, andPeter Eisentraut2002-09-24
| | | | document that scheme.
* Add earthdistance regression file.Bruce Momjian2002-09-24
|
* Add missing correction of sublevelsup when pulling up a subquery.Tom Lane2002-09-24
| | | | | | Fixes problem with cases like SELECT * FROM foo t WHERE NOT EXISTS (SELECT remoteid FROM (SELECT f1 as remoteid FROM foo WHERE f1 = t.f1) AS t1)
* Fix broken markup.Tom Lane2002-09-23
|
* Further thinking about heap_mark4update: in HeapTupleSelfUpdated case,Tom Lane2002-09-23
| | | | | | | | | executor should not return the tuple as successfully marked, because in fact it's been deleted. Not clear that this case has ever been seen in practice (I think you'd have to write a SELECT FOR UPDATE that calls a function that deletes some row the SELECT will visit later...) but we should be consistent. Also add comments to several other places that got it right but didn't explain what they were doing.
* Move PyGreSQL usage documentation from README into DocBook. Some otherPeter Eisentraut2002-09-23
| | | | editing.
* Disallow VACUUM, ANALYZE, TRUNCATE on temp tables belonging to otherTom Lane2002-09-23
| | | | | backends. Given that temp tables now store data locally in the local buffer manager, these things are not going to work safely.
* Tweak dblink functions to use int4 arguments instead of int2,Tom Lane2002-09-23
| | | | to avoid having to write explicit casts. From Joe Conway.
* Add:Bruce Momjian2002-09-23
| | | | > * Add start time to pg_stat_activity
* Update HISTORY for 7.3beta2.Bruce Momjian2002-09-23
|
* Add win32 rename discussion to archives.Bruce Momjian2002-09-23
|
* The valid return value should be MODIFY instead of MODIFIED.Bruce Momjian2002-09-23
| | | | | | | | | | | | | | | | | 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
* Obviously noone has ever tested the doubling of availiable result idsBruce Momjian2002-09-23
| | | | | | | | | | | | | | | | | | | 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
* Nothing.Bruce Momjian2002-09-23
|
* Get rid of bogus use of heap_mark4update in reindex operations (cf.Tom Lane2002-09-23
| | | | | recent bug report). Fix processing of nailed-in-cache indexes; it appears that REINDEX DATABASE has been broken for months :-(.
* In UpdateStats(), don't bother to update the pg_class row if it alreadyTom Lane2002-09-22
| | | | | | | | 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.
* Remove commas for compatibility with newer releases of bison.Tom Lane2002-09-22
|
* Remove commas for compatibility with newer bisons.Tom Lane2002-09-22
|
* Remove extraneous | ... while bison 1.28 doesn't object, newer versionsTom Lane2002-09-22
| | | | do.
* Remove commas from %type and %token lists, for compatibility with newerTom Lane2002-09-22
| | | | versions of bison.
* Translation updates, some messages tweaked.Peter Eisentraut2002-09-22
|
* RelationClearRelation must reset rd_targblock and update rd_nblocksTom Lane2002-09-22
| | | | | | 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.
* Make \dS work more like it used to, viz, show only system objects.Tom Lane2002-09-22
|
* I haven't seen any objections, so here is a patch. It removes "#defineTom Lane2002-09-22
| | | | | | | | 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
* server_min_messages and friends should have valid values at bootup.Tom Lane2002-09-22
|
* Replace pg_attribute.attisinherited with attislocal and attinhcountTom Lane2002-09-22
| | | | | columns, to allow more correct behavior in multiple-inheritance cases. Patch by Alvaro Herrera, review by Tom Lane.
* Fix busted markup.Tom Lane2002-09-22
|
* Bring SIMILAR TO and SUBSTRING into some semblance of conformance withTom Lane2002-09-22
| | | | | | | 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.
* Move most of the error checking for foreign-key constraints out ofTom Lane2002-09-22
| | | | | | | | | | | | | | | | | | | | | | 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.
* Add last-ditch defense against attempts to compile datetime code withTom Lane2002-09-21
| | | | -ffast-math.
* Provide an upgrade strategy for dump files containing functions declaredTom Lane2002-09-21
| | | | | | | | 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.
* Add more appropriate markup.Peter Eisentraut2002-09-21
|
* Fix PPC s_lock operations to work correctly on multi-CPU machines.Tom Lane2002-09-21
| | | | Need 'isync' during TAS and 'sync' during S_UNLOCK.
* Performance improvement for MultiRecordFreeSpace on large relations ---Tom Lane2002-09-20
| | | | | avoid O(N^2) behavior. Problem noted and fixed by Stephen Marshall <smarshall@wsicorp.com>, with some help from Tom Lane.
* RevisionPeter Eisentraut2002-09-20
|
* Put in defense against gcc -ffast-math.Peter Eisentraut2002-09-20
|
* Code review for check-domain-constraints-in-COPY patch. Do correct thingTom Lane2002-09-20
| | | | | when default expression for a domain is being used. Avoid repetitive catalog lookups.
* Update regression expected results for to_char() change.Tom Lane2002-09-20
|
* Change domain patch to COERCE_IMPLICIT_CAST, per Tom.Bruce Momjian2002-09-20
|
* Fix compile error from Rod's patch.Bruce Momjian2002-09-20
|
* Done:Bruce Momjian2002-09-20
| | | | > * -to_char(0,'FM999.99') returns a period, to_char(1,'FM999.99') doesn't (Karel)
* The patch fix bug described in TODO:Bruce Momjian2002-09-20
| | | | | | * to_char(0,'FM999.99') returns a period, to_char(1,'FM999.99') does not Karel Zak
* Tom Lane wrote:Bruce Momjian2002-09-20
| | | | | | | | | | | | | | | > 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
* This patch cleans up some of the code in src/util/adt/formatting.c,Bruce Momjian2002-09-20
| | | | | | | fixes a few minor bugs (typos, potential buffer overruns, etc.), and fixes some spelling/grammar mistakes. Neil Conway
* Tiny patch fixing small documentation typo.Bruce Momjian2002-09-20
| | | | Oleg Bartunov
* This patch fixes two typos in src/backend/storage/ipc/README.Bruce Momjian2002-09-20
| | | | Neil Conway
* Fixed this problem and added regression tests in domain.sql.Bruce Momjian2002-09-20
| | | | | | | | Also: - Changed header file order (alphabetical) - Changed to m = attnum - 1 in binary copy code for consistency Rod Taylor
* I have included fixes to declare some floating point constants as doubleBruce Momjian2002-09-20
| | | | | | | | | | | | instead of int, change the calculation method to use the haversine formula which is more accurrate for short distances, added a grant to public for geo_distance and added a regression test. I will resubmit the earth distance stuff based on cube after 7.3 is released. Bruno Wolff III
* > I'm not sure why NDirectFileRead/NDirectFileWrite are unused at theBruce Momjian2002-09-20
| | | | | | | | | | | | | | | > moment, but they used to be used; I think the correct response is to > put back the missing counter increments, not rip out the counters. Ok, fair enough. It's worth noting that they've been broken for a while -- for example, the HashJoin counter increments were broken when you comitted r1.20 of executor/nodeHashJoin.c in May of '99. I've attached a revised patch that doesn't remove the counters (but doesn't increment them either: I'm not sure of all the places where the counter should be incremented). Neil Conway
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 04:16:05 +0000