aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Some minor further cleanup around A_Const. Don't attach a typecast inTom Lane2008-04-29
| | | | | makeFloatConst, and avoid "manual" construction of A_Const nodes in grammar productions, in favor of using makeXXXConst subroutines.
* Fix REASSIGN OWNED so that it works on procedural languages too.Alvaro Herrera2008-04-29
| | | | | | | The capability for changing language owners is new in 8.3, so that's how far back this needs to be backpatched. Per bug #4132 by Kirill Simonov.
* Remove typename from A_Const.Alvaro Herrera2008-04-29
| | | | Brendan Jurd, minor editorialization by me.
* Fix volatility marking for the generate_series and generate_subscripts familiesAlvaro Herrera2008-04-29
| | | | of functions.
* Increase the statement_timeout value used in the prepared_xacts regressionTom Lane2008-04-28
| | | | | test. We have seen some buildfarm failures that seem to be due to this limit being unexpectedly exceeded when the machine is under load.
* Update comment for 8.4:Bruce Momjian2008-04-28
| | | | > #A hyphen, "-", marks changes that will appear in the upcoming 8.4 release.#
* Fix broken configure test for libxslt: it was probing for xsltLibxmlVersion,Tom Lane2008-04-28
| | | | | | which is a global variable not a function, and so the probe failed on machines where the linker makes a distinction (cf. Red Hat bug #444317). Probe for an actual function instead.
* Bump the catversion for the previous patch.Alvaro Herrera2008-04-28
|
* Add generate_subscripts, a series-generation function which generates anAlvaro Herrera2008-04-28
| | | | | | array's subscripts. Pavel Stehule, some editorialization by me.
* Add SGML ID attributes to the arrays subsections, and a few index entries forAlvaro Herrera2008-04-27
| | | | them.
* Code review for recent patch to terminate online backup during shutdown:Tom Lane2008-04-26
| | | | | do CancelBackup at a sane place, fix some oversights in the state transitions, allow only superusers to connect while we are waiting for backup mode to end.
* Add URL for:Bruce Momjian2008-04-25
| | | | | | | | * Allow adding/renaming/removing enumerated values to an existing enumerated data type > > http://archives.postgresql.org/pgsql-hackers/2008-04/msg01718.php >
* Update wording from David Fetter.Bruce Momjian2008-04-25
|
* Update to remove passive wording from FAQ, David FetterBruce Momjian2008-04-25
|
* Update TODO item:Bruce Momjian2008-04-24
| | | | | > * Allow adding/renaming/removing enumerated values to an existing > enumerated data type
* Remove transformAlterTableStmt's kluge to replace ColumnDef.is_not_nullTom Lane2008-04-24
| | | | | | | | | flags by separate AT_SetNotNull subcommands. That was always ugly and inefficient, and it's now clear that it was merely a partial workaround for the bug just identified in ATExecAddColumn. This is just code beautification not a bug fix, so no back-patch. Brendan Jurd, with some trivial additional cleanup by me.
* Update:Bruce Momjian2008-04-24
| | | | | < * Allow adding enumerated values to an existing enumerated data > * Allow adding/removing enumerated values to an existing enumerated data
* Fix ALTER TABLE ADD COLUMN ... PRIMARY KEY so that the new column is correctlyTom Lane2008-04-24
| | | | | | | | | | checked to see if it's been initialized to all non-nulls. The implicit NOT NULL constraint was not being checked during the ALTER (in fact, not even if there was an explicit NOT NULL too), because ATExecAddColumn neglected to set the flag needed to make the test happen. This has been broken since the capability was first added, in 8.0. Brendan Jurd, per a report from Kaloyan Iliev.
* Add embedded usage mention to FAQ, per Greg Smith.Bruce Momjian2008-04-24
|
* Add to TODO:Bruce Momjian2008-04-24
| | | | | | | | > * Allow prepared transactions with temporary tables created and dropped > in the same transaction, and when an ON COMMIT DELETE ROWS temporary > table is accessed > > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00047.php
* Add TODO item:Bruce Momjian2008-04-24
| | | | | | | > > o Impove COPY performance > > http://archives.postgresql.org/pgsql-hackers/2008-02/msg00954.php
* Add URL for:Bruce Momjian2008-04-24
| | | | | | | | * Allow index scans to return matching index keys, not just the matching heap locations > > http://archives.postgresql.org/pgsql-hackers/2008-04/msg01657.php >
* Add to TODO:Bruce Momjian2008-04-24
| | | | | > * Allow index scans to return matching index keys, not just the matching > heap locations
* Add to TODO:Bruce Momjian2008-04-24
| | | | | | < > * Allow adding enumerated values to an existing enumerated data > type
* Remove, item done, description unclear:Bruce Momjian2008-04-24
| | | | | | < * Allow index scans to return matching index keys < < http://archives.postgresql.org/pgsql-hackers/2007-03/msg01079.php
* Update TODO description for GIT:Bruce Momjian2008-04-24
| | | | | * Consider smaller indexes that record a range of values per heap page, rather than having one index entry for every heap row
* Update error messages, per notes from Tom.Magnus Hagander2008-04-24
| | | | Laurenz Albe
* Add GIT URL:Bruce Momjian2008-04-24
| | | | > http://archives.postgresql.org/pgsql-hackers/2008-04/msg01589.php
* Add to TODO:Bruce Momjian2008-04-24
| | | | | < > o Add prompt escape to display the client and server versions
* Add URL for MERGE:Bruce Momjian2008-04-23
| | | | > http://archives.postgresql.org/pgsql-hackers/2008-04/msg01475.php
* Prevent shutdown in normal mode if online backup is running, andMagnus Hagander2008-04-23
| | | | | | | | | have pg_ctl warn about this. Cancel running online backups (by renaming the backup_label file, thus rendering the backup useless) when shutting down in fast mode. Laurenz Albe
* Fix using too many LWLocks bug, reported by Craig RingerTeodor Sigaev2008-04-22
| | | | | | | | | <craig@postnewspapers.com.au>. It was my mistake, I missed limitation of number of held locks, now GIN doesn't use continiuous locks, but still hold buffers pinned to prevent interference with vacuum's deletion algorithm. Backpatch is needed.
* Don't pull in pthreads header files in this file because we never use them.Magnus Hagander2008-04-22
|
* FAQ2txt now only controls the main FAQ, not FAQ_DEV.Bruce Momjian2008-04-22
|
* Replace developer FAQ with a reference to the wiki, which is whereMagnus Hagander2008-04-22
| | | | it now lives (per discussion). Leave the other FAQs alone for now.
* Issue explicit error messages for attempts to use "shell" operators inTom Lane2008-04-22
| | | | | | | | | | ordinary expressions. This probably doesn't catch every single case where you might get "cache lookup failed for function 0" for use of a shell operator, but it will catch most. Per bug #4120 from Pedro Gimeno. This patch incidentally folds make_op_expr() into its sole remaining caller --- the alternative was to give it yet more arguments, which didn't seem an improvement.
* Fix convert_IN_to_join to properly handle the case where the subselect'sTom Lane2008-04-21
| | | | | | | | | | | | | | | | | | | | | | | | | output is not of the same type that's needed for the IN comparison (ie, where the parser inserted an implicit coercion above the subselect result). We should record the coerced expression, not just a raw Var referencing the subselect output, as the quantity that needs to be unique-ified if we choose to implement the IN as Unique followed by a plain join. As of 8.3 this error was causing crashes, as seen in bug #4113 from Javier Hernandez, because the executor was being told to hash or sort the raw subselect output column using operators appropriate to the coerced type. In prior versions there was no crash because the executor chose the hash or sort operators for itself based on the column type it saw. However, that's still not really right, because what's unique for one data type might not be unique for another. In corner cases we could get multiple outputs of a row that should appear only once, as demonstrated by the regression test case included in this commit. However, this patch doesn't apply cleanly to 8.2 or before, and the code involved has shifted enough over time that I'm hesitant to try to back-patch. Given the lack of complaints from the field about such corner cases, I think the bug may not be important enough to risk breaking other things with a back-patch.
* Clean up float4byval and float8byval handling by dealing with them completelyMagnus Hagander2008-04-21
| | | | from inside the build script.
* Fix typo, noted by Stefan Kaltenbrunner.Magnus Hagander2008-04-21
|
* Make float4byval and float8byval configurable on MSVC.Magnus Hagander2008-04-21
|
* Add link to major version release notes at the top of the minorMagnus Hagander2008-04-21
| | | | | | version ones, to make it clear to users just browsing the notes that there are a lot more changes available from whatever version they are at than what's in the minor version release notes.
* Fix a couple of places in execMain that erroneously assumed that SELECT FORTom Lane2008-04-21
| | | | | | | | | | UPDATE/SHARE couldn't occur as a subquery in a query with a non-SELECT top-level operation. Symptoms included outright failure (as in report from Mark Mielke) and silently neglecting to take the requested row locks. Back-patch to 8.3, because the visible failure in the INSERT ... SELECT case is a regression from 8.2. I'm a bit hesitant to back-patch further given the lack of field complaints.
* Add FLOAT4PASSBYVAL/FLOAT8PASSBYVAL to pg_config.h.win32, as a stopgapTom Lane2008-04-21
| | | | | | measure to get the Windows buildfarm members working again. I don't know if it's worth exposing these as configurables, or exactly how to do it in the MSVC build system ...
* Make earthdistance use version-0 calling convention if not USE_FLOAT8_BYVAL,Tom Lane2008-04-21
| | | | | | | | | | and version-1 if USE_FLOAT8_BYVAL. This might seem a bit pointless, but the idea is to have at least one regression test that will fail if we ever accidentally break version-0 functions that return float8. However, they're already broken, or at least hopelessly unportable, in the USE_FLOAT8_BYVAL case. Per a recent suggestion from Greg Stark.
* Allow float8, int8, and related datatypes to be passed by value on machinesTom Lane2008-04-21
| | | | | | | | | | where Datum is 8 bytes wide. Since this will break old-style C functions (those still using version 0 calling convention) that have arguments or results of these types, provide a configure option to disable it and retain the old pass-by-reference behavior. Likewise, provide a configure option to disable the recently-committed float4 pass-by-value change. Zoltan Boszormenyi, plus configurability stuff by me.
* Fix broken compare function for tsquery_ops. Per Tom's report.Teodor Sigaev2008-04-20
| | | | | | | | | | I never understood why initial authors GiST in pgsql choose so stgrange signature for 'same' method: bool *sameFn(Datum a, Datum b, bool* result) instead of simple, logical bool sameFn(Datum a, Datum b) This change will break any existing GiST extension, so we still live with it and will live.
* Convert earthdistance's only C function to v1 call convention,Tom Lane2008-04-20
| | | | to future-proof it against pass-by-value float8.
* seg_size() has to be V1 calling convention, too.Tom Lane2008-04-19
|
* Update doc script comments.Bruce Momjian2008-04-19
|
* Add script FAQ2txt to convert HTML files to txt. Add comment to TODO2html.Bruce Momjian2008-04-19
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 05:27:44 +0000