aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* During ALTER TABLE ADD FOREIGN KEY, try to check the existing rows usingTom Lane2003-10-06
| | | | | | a single LEFT JOIN query instead of firing the check trigger for each row individually. Stephan Szabo, with some kibitzing from Tom Lane and Jan Wieck.
* New Slovene translationsPeter Eisentraut2003-10-06
|
* - Fixed constant listing in execute using clause.Michael Meskes2003-10-06
| | | | | - Fixed typo in ecpg for Informix dec_t type. - Fixed precision handling in Informix compat funxtions.
* Translation updatesPeter Eisentraut2003-10-06
|
* Modify COPY FROM to match the null-value string against the column valueTom Lane2003-10-06
| | | | | | | | | | | before it is de-backslashed, not after. This allows the null string \N to be reliably distinguished from the data value \N (which must be represented as \\N). Per bug report from Manfred Koizar ... but it's amazing this hasn't been reported before ... Also, be consistent about encoding conversion for null string: the form specified in the command is in the server encoding, but what is sent to/from client must be in client encoding. This never worked quite right before either.
* Fix order of operations within SendQuery() so that the time spent inTom Lane2003-10-06
| | | | | data transfer during COPY is included in the \timing display. Also avoid portability problems if tv_usec is unsigned on some platform.
* Add a little more smarts to estimate_hash_bucketsize(): if there's noTom Lane2003-10-05
| | | | | statistics, but there is a unique index on the column, we can safely assume it's well-distributed.
* Make psql \timing show three digits.Bruce Momjian2003-10-05
|
* Translation updatesPeter Eisentraut2003-10-05
|
* When revoking privileges from the owner, don't revoke the grant options,Peter Eisentraut2003-10-05
| | | | to avoid recursively revoking everything from everyone.
* Fixed bug in day of week processing.Michael Meskes2003-10-05
|
* Translation updatePeter Eisentraut2003-10-04
|
* Document the always-true-but-previously-undocumented fact that PQfnumber()Tom Lane2003-10-04
| | | | | | | will downcase the supplied field name unless it is double-quoted. Also, upgrade the routine's handling of double quotes to match the backend, in particular support doubled double quotes within quoted identifiers. Per pgsql-interfaces discussion a couple weeks ago.
* Fix pg_get_constraintdef() to ensure CHECK constraints are always shownTom Lane2003-10-04
| | | | | | | with required outer parentheses. Breakage seems to be leftover from domain-constraint patches. This could be smarter about suppressing extra parens, but at this stage of the release cycle I want certainty not cuteness.
* Translation updatesPeter Eisentraut2003-10-04
|
* Translation updatePeter Eisentraut2003-10-04
|
* Fix log_duration and log_min_duration_statement to print properly, asBruce Momjian2003-10-04
| | | | pointed out by Peter.
* Translation updatesPeter Eisentraut2003-10-04
|
* Format help message internally consistent.Peter Eisentraut2003-10-04
|
* Change transaction status indicator in prompt from %T to %x.Peter Eisentraut2003-10-04
|
* New translationPeter Eisentraut2003-10-03
|
* Issue 'SET check_function_bodies = false' to suppress possible restoreTom Lane2003-10-03
| | | | | failures in SQL functions, due to forward references or unqualified references to objects in other schemas. Per recent discussion.
* Add GUC parameter check_function_bodies to control whether validationTom Lane2003-10-03
| | | | | | | of function bodies is done at CREATE FUNCTION time. This is normally true but can be set false to avoid problems with forward references, wrong schema search path, etc. This is just the backend patch, still need to adjust pg_dump to make use of it.
* Cause PQescapeString to stop processing at a null character, ratherTom Lane2003-10-03
| | | | | | than generating an invalid output string. Per observation and patch from Igor Shevchenko. Further code cleanup and documentation by Tom Lane.
* Remove assorted compilation failures introduced by latest ecpg changes.Tom Lane2003-10-03
| | | | | Also remove -g, which has no business in CPPFLAGS in the first place, let alone being hardwired there by a sub-Makefile.
* Hide Informix datatypes. They are not seen by our built process anymore.Michael Meskes2003-10-03
|
* Add a bit more locking to vac_update_relstats and vac_update_dbstatsTom Lane2003-10-02
| | | | | | | to make them comparable to what UpdateStats does in the same situation. I'm not certain two instances of vac_update_relstats could run in parallel for the same relation, but parallel invocations of vac_update_dbstats do seem possible.
* When dumping CREATE INDEX, must show opclass name if the opclass isn'tTom Lane2003-10-02
| | | | | | in the schema search path. Otherwise pg_dump doesn't correctly dump scenarios where a custom opclass is created in 'public' and then used by indexes in other schemas.
* Do not return from PQrequestCancel until postmaster has finishedTom Lane2003-10-02
| | | | | | processing the request; this ensures that the request won't be taken to cancel a subsequently-issued query. Race condition originally noted by Oliver Jowett in the context of JDBC, but libpq has it too.
* Don't use 0 as a spelling of NULL.Tom Lane2003-10-02
|
* Add documentation about \pset footer to \?.Peter Eisentraut2003-10-02
| | | | from Patrick Welche
* String fixes/improvements found by Alvaro HerreraPeter Eisentraut2003-10-02
|
* Change some notices to warnings and vice versa according to criteriaPeter Eisentraut2003-10-02
| | | | developed on -hackers.
* Remove NOTICE about foreign key creating implicit triggers, because it noPeter Eisentraut2003-10-02
| | | | longer conveys useful information.
* Add code to check that IF/WHILE/EXIT test expressions are boolean,Tom Lane2003-10-01
| | | | and try to coerce the values to boolean if not. Per recent discussions.
* Repair RI trigger visibility problems (this time for sure ;-)) per recentTom Lane2003-10-01
| | | | | | | discussion on pgsql-hackers: in READ COMMITTED mode we just have to force a QuerySnapshot update in the trigger, but in SERIALIZABLE mode we have to run the scan under a current snapshot and then complain if any rows would be updated/deleted that are not visible in the transaction snapshot.
* heap_open => relation_open to avoid unwanted restriction on relkind.Tom Lane2003-09-30
| | | | Per gripe from Gaetano Mendola.
* Adjust btree index build procedure so that the btree metapage looksTom Lane2003-09-29
| | | | | | | | | | invalid (has the wrong magic number) until the build is entirely complete. This turns out to cost no additional writes in the normal case, since we were rewriting the metapage at the end of the process anyway. In normal scenarios there's no real gain in security, because a failed index build would roll back the transaction leaving an unused index file, but for rebuilding shared system indexes this seems to add some useful protection.
* Improve context display for failures during COPY IN, as recentlyTom Lane2003-09-29
| | | | discussed on pghackers.
* Fixed type lookup in spi_prepare for possible qualifiedJan Wieck2003-09-29
| | | | | | type name specification. Jan
* The brackets aren't put on the CHECK constraints properly.Bruce Momjian2003-09-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before patch: test=# select pg_get_constraintdef(oid) from pg_constraint; pg_get_constraintdef ------------------------------------------------------------------------------------------------- CHECK (VALUE >= 0) CHECK ((((a)::text = 'asdf'::text) OR ((a)::text = 'fdsa'::text)) OR ((a)::text = 'dfd'::text)) PRIMARY KEY (b) FOREIGN KEY (a) REFERENCES test2(b) UNIQUE (b) (5 rows) test=# select pg_get_constraintdef(oid, true) from pg_constraint; pg_get_constraintdef ----------------------------------------------------------------------------------- CHECK VALUE >= 0 CHECK a::text = 'asdf'::text OR a::text = 'fdsa'::text OR a::text = 'dfd'::text PRIMARY KEY (b) FOREIGN KEY (a) REFERENCES test2(b) UNIQUE (b) (5 rows) After patch: test=# select pg_get_constraintdef(oid) from pg_constraint; pg_get_constraintdef ------------------------------------------------------------------------------------------------- CHECK (VALUE >= 0) CHECK ((((a)::text = 'asdf'::text) OR ((a)::text = 'fdsa'::text)) OR ((a)::text = 'dfd'::text)) PRIMARY KEY (b) FOREIGN KEY (a) REFERENCES test2(b) UNIQUE (b) (5 rows) test=# select pg_get_constraintdef(oid, true) from pg_constraint; pg_get_constraintdef ----------------------------------------------------------------------------------- CHECK (VALUE >= 0) ` CHECK (a::text = 'asdf'::text OR a::text = 'fdsa'::text OR a::text = 'dfd'::text) PRIMARY KEY (b) FOREIGN KEY (a) REFERENCES test2(b) UNIQUE (b) (5 rows) It's important that those brackets are there to (a) match all other constraints and (b) so that people can just copy and paste them and it will work as SQL. Christopher Kings-Lynne
* This patch fixes an obvious bug in the "should I print the duration ofBruce Momjian2003-09-29
| | | | | | | | this query?" logic in postgres.c Also, make it print "duration:" like log_duration. Neil Conway
* I discovered that TupleDescGetAttInMetadata and BuildTupleFromCStringsBruce Momjian2003-09-29
| | | | | | | don't deal well with tuples having dropped columns. The attached fixes the issue. Please apply. Joe Conway
* > >Bruce Momjian2003-09-29
| | | | | | | | | | | | | | | | | | | | | | | | | | > > a) Write documentation how the win32 console needs to be set up so that > > psql can handle 8-bit characters. > > Where should it be added? The Section "Installation on Windows" in the > > Administrator's Guide seems natural to me. > > > > b) Add code to psql that prints a warning on startup of psql when the > > console codepage differs from the windows codepage, something like > > > > Warning: Console codepage (850) differs from windows codepage (1252) > > 8-bit characters will not work correctly. See PostgreSQL > > documentation "Installation on Windows" for details. > Attached are two patches: - installdoc.patch contains an additional paragraph on the win32 console codepage for the chapter "Installation on Windows" Due to a lack of SGML-tools, I have only edited the text and not tested the SGML code - please check it before merging into the CVS branch. - psqlcodepage.patch adds the warning about a problematic codepage to psql. Christoph Dalitz
* Adjust the new Norwegian translation for some of the easier messagePeter Eisentraut2003-09-29
| | | | changes between 7.3 and 7.4, for example quoting and function names.
* Apparently, gettext doesn't like double parentheses around argument. WhatPeter Eisentraut2003-09-29
| | | | were they doing here anyway?
* Make message fit guidelines.Peter Eisentraut2003-09-29
|
* Eliminate another gratuitous message wording difference.Peter Eisentraut2003-09-29
|
* New Norwegian translation by Trond Endrestøl, actually made for 7.3, butPeter Eisentraut2003-09-29
| | | | this should help people get started in 7.4 as well.
* New translationsPeter Eisentraut2003-09-29
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-22 20:54:09 +0000