aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
* Fix timestamp_date for HAVE_INT64_TIMESTAMP case.REL7_3_4Tom Lane2003-07-24
|
* Repair 7.3 breakage in timestamp-to-date conversion for dates before 2000.Tom Lane2003-07-24
|
* wups, took out one memset too many ...Tom Lane2003-07-22
|
* Back-patch fix for bugs in pgstat_initstats.Tom Lane2003-07-22
|
* Oh, for crying in a bucket ... relax Assert so that glibc's strxfrmTom Lane2003-07-17
| | | | does not dump core.
* Work around buggy strxfrm() present in some Solaris releases.Tom Lane2003-07-17
|
* For COMMENT ON DATABASE where database name is unknown or not the currentTom Lane2003-07-17
| | | | | | database, emit a WARNING and do nothing, rather than raising ERROR. Per recent discussion in which we concluded this is the best way to deal with database dumps that are reloaded into a database of a new name.
* Repair boundary-case bug introduced by patch of two months ago thatTom Lane2003-07-17
| | | | | | | | fixed incorrect initial setting of StartUpID. The logic in XLogWrite() expects that Write->curridx is advanced to the next page as soon as LogwrtResult points to the end of the current page, but StartupXLOG() failed to make that happen when the old WAL ended exactly on a page boundary. Per trouble report from Hannu Krosing.
* Fix a *second* buffer overrun bug in to_ascii(). Grumble.Tom Lane2003-07-14
|
* Don't generate 'zero' typeids in the output from gen_cross_product.Tom Lane2003-06-25
| | | | | | This is no longer necessary or appropriate since we don't use zero typeid as a wildcard anymore, and it fixes a nasty performance problem with functions with many parameters. Per recent example from Reuven Lerner.
* Fix bugs in interval-to-time conversion: HAVE_INT64_TIMESTAMP case did notTom Lane2003-06-16
| | | | work at all, and neither case behaved sanely for negative intervals.
* Fix SQL function executor for case where last command of a function isTom Lane2003-06-12
| | | | not a SELECT. We didn't use to allow that, but we do now.
* Add defense in assign_session_authorization() against trying to doTom Lane2003-06-06
| | | | | | catalog lookups when not in a transaction. This prevents bizarre failures if someone tries to set a value for session_authorization in postgresql.conf. Per report from Fernando Nasser.
* Repair sometimes-incorrect computation of StartUpID after a crash, perTom Lane2003-05-22
| | | | | | | example from Rao Kumar. This is a very corner corner-case, requiring a minimum of three closely-spaced database crashes and an unlucky positioning of the second recovery's checkpoint record before you'd notice any problem. But the consequences are dire enough that it's a must-fix.
* Back-patch Jan's fix to avoid primary key lookup (and lock) if foreign keyTom Lane2003-05-21
| | | | does not change on UPDATE.
* Back-patch change to avoid O(N^2) behavior with lots of deferred triggers,Tom Lane2003-05-19
| | | | by making deferredTriggerInvokeEvents only scan events added since it last ran.
* Apply fixes for problems with dropped columns whose types have also beenTom Lane2003-05-12
| | | | dropped. Add regression test, too.
* Adjust CreateCheckpoint so that buffer dumping activities and cleanup ofTom Lane2003-05-10
| | | | | | dead xlog segments are not considered part of a critical section. It is not necessary to force a database-wide panic if we get a failure in these operations. Per recent trouble reports.
* Allow 60 in seconds fields of timestamp, time, interval input values.Tom Lane2003-05-04
| | | | | | Per recent discussion on pgsql-general, this is appropriate for spec compliance, and has the nice side-effect of easing porting from old pg_dump files that exhibit the 59.999=>60.000 roundoff problem.
* When a TIMESTAMP, TIME, or INTERVAL precision is specified larger than ourTom Lane2003-05-04
| | | | | | | | | | | | implementation limits, do not issue an ERROR; instead issue a NOTICE and use the max supported value. Per pgsql-general discussion of 28-Apr, this is needed to allow easy porting from pre-7.3 releases where the limits were higher. Unrelated change in same area: accept GLOBAL TEMP/TEMPORARY as a synonym for TEMPORARY, as per pgsql-hackers discussion of 15-Apr. We previously rejected it, but that was based on a misreading of the spec --- SQL92's GLOBAL temp tables are really closer to what we have than their LOCAL ones.
* Repair permissions problem in RI triggers: query parsing has to be doneTom Lane2003-04-26
| | | | | as the correct user, not only query execution. Per report from Sean Chittenden.
* Back-patch fixes for zero-column tables in COPY, pg_dump.Tom Lane2003-04-25
|
* Make [VACUUM] ANALYZE safe on zero-column tables.Tom Lane2003-04-25
|
* Fix misbehavior of func_error() on type names containing '%'.Tom Lane2003-04-23
| | | | Will patch separately but equivalently in HEAD.
* Fix misbehavior of replace() on strings containing '%'.Tom Lane2003-04-23
| | | | Will patch separately but equivalently in HEAD.
* Prevent palloc(0) error when parent table has zero columns.Tom Lane2003-04-21
|
* Fix char-vs-pg_wchar confusion in p_ere(), per failure report fromTom Lane2003-04-20
| | | | | Tom O'Dowd. This fix is not relevant to CVS tip anymore, but we should fix it in 7.3.*.
* Fix stupid oversight ...Tom Lane2003-04-16
|
* eqjoinsel's logic for case where MCV lists are not present shouldTom Lane2003-04-15
| | | | | | account for NULLs; in hindsight this is obvious since the code for the MCV-lists case would reduce to this when there are zero entries in both lists. Per example from Alec Mitchell.
* Second try at avoiding conflicts with system isblank().Tom Lane2003-04-13
|
* Guard against macro versions of isblank().Tom Lane2003-04-12
|
* Fix encoding conversion function bug.Tatsuo Ishii2003-04-12
| | | | | | | | | | See following posting for more details. Subject: Re: [HACKERS] [BUGS] Bug #943: Server-Encoding from EUC_TW to UTF-8 doesn't From: Tatsuo Ishii <t-ishii@sra.co.jp> To: michael.enke@wincor-nixdorf.com, pgsql-bugs@postgresql.org Cc: pgsql-hackers@postgresql.org Date: Sat, 12 Apr 2003 10:51:45 +0900 (JST)
* Fix error recovery for SSL_read/SSL_write calls.Tom Lane2003-04-10
|
* Remove premature attempt to constant-fold type coercion expressions.Tom Lane2003-04-10
| | | | | While usually safe, this fails if the coercion function needs the query snapshot to be set already. Per example from Nigel Andrews.
* Back-patch changes to validate page header fields immediately afterTom Lane2003-04-04
| | | | | reading in any page. Also back-port the zero_damaged_pages boolean that determines what to do about it.
* Repair incorrect checking of grouped/ungrouped variables in the presenceTom Lane2003-04-03
| | | | of unnamed joins; per pghackers discussion 31-Mar-03.
* Fix buffer overrun in to_ascii(), per report from Guido Notari.Tom Lane2003-04-02
|
* TestConfiguration returns int, not bool. This mistake is relativelyTom Lane2003-03-31
| | | | | | | harmless on signed-char machines but would lead to core dump in the deadlock detection code if char is unsigned. Amazingly, this bug has been here since 7.1 and yet wasn't reported till now. Thanks to Robert Bruccoleri for providing the opportunity to track it down.
* Properly document default value of log_min_error_statement in postgresql.conf.Bruce Momjian2003-03-30
|
* Backpatch SSL return value changes.Bruce Momjian2003-03-30
|
* [ Backpatch to 7.3.X.]Bruce Momjian2003-03-29
| | | | | | | | | | | typing error in src/backend/libpq/be-secure.c ??? Long Description In src/backend/libpq/be-secure.c: secure_write on SSL_ERROR_WANT_WRITE call secure_read instead secure_write again. May be is this a typing error? Sergey N. Yatskevich (syatskevich@n21lab.gosniias.msk.ru)
* Fix bogus coding of SET DEFAULT ri triggers ... or at least make it lessTom Lane2003-03-27
| | | | bogus than it was. Per bug report from Adrian Pop.
* GetTupleForTrigger must use outer transaction's command counter for timeTom Lane2003-03-27
| | | | qual checking, not GetCurrentCommandId. Per test case from Steve Wolfe.
* Band-aid patch for Shraibman's 'out of free buffers' bug: disable theTom Lane2003-03-23
| | | | | | keys_are_unique optimization introduced in 7.3. A better fix will appear in 7.4, but I think back-patching it is too risky for the stable branch.
* Tweak selectivity and related routines to cope with domains. Per reportTom Lane2003-03-23
| | | | from Andreas Pflug.
* Prevent infinite loop in ln_var() due to roundoff error.Tom Lane2003-03-14
| | | | Per report from Dave Marin.
* GROUP BY got confused if there were multiple equal() GROUP BY items.Tom Lane2003-03-13
| | | | | | This bug has been latent since 7.0 or maybe even further back, but it was only exposed when parse_clause.c stopped suppressing duplicate items (see its rev 1.96 of 18-Aug-02).
* Tweak dependency code to suppress NOTICEs generated by new method forTom Lane2003-03-06
| | | | | | cleaning out temp namespaces. We don't really want the server log to be cluttered with 'Drop cascades to table foo' every time someone uses a temp table...
* Repair bug reported by Laurent Perez: bad plan generated when UPDATE orTom Lane2003-03-05
| | | | | | DELETE of an inheritance tree references another inherited relation. This bug has been latent since 7.1; I'm still not quite sure why 7.1 and 7.2 don't manifest it (at least, they don't crash on a simple test case).
* Prevent clustering on incomplete indexes: partial indexes are verboten,Tom Lane2003-03-03
| | | | as are non-amindexnulls AMs unless first column is attnotnull.