aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
* Mark the float8 -> int8 cast as implicit. This resolves the problemTom Lane2002-09-01
| | | | | | | | | | pointed out by Barry Lind: UPDATE bigintcol = 10000000000 fails because the constant is initially taken as float8. We really need a better way, but it's not gonna happen for 7.3. Also, remove int4reltime() function, which is redundant with the existing binary-compatibility coercion path from int4 to reltime, and probably has been unreachable code for a long while.
* Code review for domain-constraints patch. Use a new ConstraintTest nodeTom Lane2002-08-31
| | | | | | | | | type for runtime constraint checks, instead of misusing the parse-time Constraint node for the purpose. Fix some damage introduced into type coercion logic; in particular ensure that a coerced expression tree will read out the correct result type when inspected (patch had broken some RelabelType cases). Enforce domain NOT NULL constraints against columns that are omitted from an INSERT.
* Wups, didn't mean to commit that just yet.Tom Lane2002-08-31
|
* The UNDEFOID later causes an assertion failure in heap_formtuple whenTom Lane2002-08-31
| | | | | | you try to use the tupdesc to build a tuple. Joe Conway
* Code review for pg_locks feature. Make shmemoffset of PROCLOCK structsTom Lane2002-08-31
| | | | | | | | available (else there's no way to interpret the list links). Change pg_locks view to show transaction ID locks separately from ordinary relation locks. Avoid showing N duplicate rows when the same lock is held multiple times (seems unlikely that users care about exact hold count). Improve documentation.
* Add expected tuple descriptor to ReturnSetInfo information for tableTom Lane2002-08-30
| | | | | | functions, per suggestion from John Gray and Joe Conway. Also, fix plpgsql RETURN NEXT to verify that returned values match the expected tupdesc.
* AUTOCOMMIT mode is now an available backend GUC variable; setting itTom Lane2002-08-30
| | | | | | | | | to false provides more SQL-spec-compliant behavior than we had before. I am not sure that setting it false is actually a good idea yet; there is a lot of client-side code that will probably be broken by turning autocommit off. But it's a start. Loosely based on a patch by David Van Wie.
* Fix for breakage of C-coded SRFs, from Joe Conway.Tom Lane2002-08-30
|
* Add attisinherited column to pg_attribute; use it to guard againstTom Lane2002-08-30
| | | | | | column additions, deletions, and renames that would let a child table get out of sync with its parent. Patch by Alvaro Herrera, with some kibitzing by Tom Lane.
* Complete TODO item:Bruce Momjian2002-08-30
| | | | | * Remove wal_files postgresql.conf option because WAL files are now recycled
* Back out password packet length check.Bruce Momjian2002-08-30
| | | | Improve wording of pre-7.3 syntax mention.
* Group-manipulating code neglected to fill in array element type,Tom Lane2002-08-30
| | | | which is now required.
* PL/pgSQL functions can return sets. Neil Conway's patch, modified soTom Lane2002-08-30
| | | | | that the functionality is available to anyone via ReturnSetInfo, rather than hard-wiring it to PL/pgSQL.
* Fix a bug introduced in 7.2.Hiroshi Inoue2002-08-29
|
* Sir Mordred The Traitor <mordred@s-mail.com> writes:Bruce Momjian2002-08-29
| | | | | | | | | | | | | | | | | > Upon invoking a polygon(integer, circle) function a > src/backend/utils/adt/geo_ops.c:circle_poly() function will gets > called, which suffers from a buffer overflow. > > 2) A src/backend/adt/utils/geo_ops.c:path_encode() fails to detect a > buffer overrun condition. It is called in multiple places, the most > interesting are path_out() and poly_out() functions. > 5) A src/backend/utils/adt/geo_ops.c:path_add() also fails to detect > a simple buffer overrun. I've attached a patch which should fix these problems. Neil Conway
* Prevent problem with extra-long password packets from allocating lots ofBruce Momjian2002-08-29
| | | | | | memory. Neil Conway
* This patch reserves the last superuser_reserved_connections slots forBruce Momjian2002-08-29
| | | | | | | | | | | | | | | | | | | connections by the superuser only. This patch replaces the last patch I sent a couple of days ago. It closes a connection that has not been authorised by a superuser if it would leave less than the GUC variable ReservedBackends (superuser_reserved_connections in postgres.conf) backend process slots free in the SISeg. This differs to the first patch which only reserved the last ReservedBackends slots in the procState array. This has made the free slot test more expensive due to the use of a lock. After thinking about a comment on the first patch I've also made it a fatal error if the number of reserved slots is not less than the maximum number of connections. Nigel J. Andrews
* Adjust nodeFunctionscan.c to reset transient memory context between callsTom Lane2002-08-29
| | | | | | | to the table function, thus preventing memory leakage accumulation across calls. This means that SRFs need to be careful to distinguish permanent and local storage; adjust code and documentation accordingly. Patch by Joe Conway, very minor tweaks by Tom Lane.
* Push down outer qualification clauses into UNION and INTERSECT subqueries.Tom Lane2002-08-29
| | | | Per pghackers discussion from back around 1-August.
* Cause REINDEX to regard TOAST tables as regular relations, not systemTom Lane2002-08-29
| | | | | tables that need special defenses. I believe this is okay even for TOAST tables that belong to system tables.
* Remove #ifdef MULTIBYTE per hackers list discussion.Tatsuo Ishii2002-08-29
|
* Rephrase 'Cannot insert into a view' and related messages, perTom Lane2002-08-29
| | | | pghackers discussion around 31-Jul-02.
* Produce a somewhat-useful error message, namelyTom Lane2002-08-29
| | | | | | ERROR: Cannot display a value of type RECORD rather than a random integer when someone tries to SELECT a tuple value. Per pghackers discussion around 26-May-02.
* Remove support for version-0 FE/BE protocol, per pghackers discussion.Tom Lane2002-08-29
| | | | This breaks support for 6.2 or older client libraries.
* Fix ruleutils to dump column definition lists for anonymous record typesTom Lane2002-08-29
| | | | defined in the FROM clause. From Joe Conway, with some tweaks.
* Code review for standalone composite types, query-specified compositeTom Lane2002-08-29
| | | | | types, SRFs. Not happy with memory management yet, but I'll commit these other changes.
* Initial Spanish translation from Karim Mribti <karim@inlosa.com>Peter Eisentraut2002-08-28
|
* Remove TIOGA files from CVS current; they remain in repositiry.Bruce Momjian2002-08-28
|
* This trivial patches fixes the error message returned by CREATE INDEXBruce Momjian2002-08-28
| | | | | | | | | | | | | | | | when it finds an existing relation with the same name as the to-be-created index. Old error message: nconway=# create table foo (a int); CREATE TABLE nconway=# create index foo on foo (a); ERROR: index named "foo" already exists I replaced 'index' with 'relation' in the error message. Neil Conway
* backend where a statically sized buffer is written to. Most of theseBruce Momjian2002-08-28
| | | | | | | | | | | should be pretty safe in practice, but it's probably better to be safe than sorry. I was actually looking for cases where NAMEDATALEN is assumed to be 32, but only found one. That's fixed too, as well as a few bits of code cleanup. Neil Conway
* The following small patch provides a couple of minor updates (againstBruce Momjian2002-08-28
| | | | | | | | | | | | | | CVS HEAD): Amended "strings" regression test. TOAST tests now insert two values with storage set to "external", to exercise properly the TOAST slice routines which fetch only a subset of the chunks. Changed now-misleading comment on AlterTableCreateToastTable in tablecmds.c, because both columns of the index on a toast table are now used. John Gray
* Allow FOR UPDATE to appear after LIMIT/OFFSET to match MySQL syntax and asBruce Momjian2002-08-28
| | | | a more logical ordering.
* Bring comments back in sync with code.Tom Lane2002-08-27
|
* Throw error on pg_atoi(''), regression adjustments.Bruce Momjian2002-08-27
|
* The attached patch implements the password packet length sanity checkBruce Momjian2002-08-27
| | | | | | (using an elog(LOG) ), as well as includes a few more comment fixes. Neil Conway
* Add most of Neil Conway's cleanups.Bruce Momjian2002-08-27
|
* Add fsm sizes.Bruce Momjian2002-08-27
|
* PREPARE/EXECUTE statements. Patch by Neil Conway, some kibitzingTom Lane2002-08-27
| | | | from Tom Lane.
* This patch updates the lock listing code to use Joe Conway's newBruce Momjian2002-08-27
| | | | | | | | anonymous return type SRF code. It gets rid of the superflous 'pg_locks_result' that Bruce/Tom had commented on. Otherwise, no changes in functionality. Neil Conway
* This patches replaces a few more usages of strcpy() and sprintf() whenBruce Momjian2002-08-27
| | | | | | | | copying into a fixed-size buffer (in this case, a buffer of NAMEDATALEN bytes). AFAICT nothing to worry about here, but worth fixing anyway... Neil Conway
* I attach a little patch to make CLUSTER set and reset the indisclusteredBruce Momjian2002-08-27
| | | | | | | | | | | | | | | | | bit on the indexes. I also attach clusterdb and clusterdb.sgml; both of them are blatant rips of vacuumdb and vacuumdb.sgml, but get the job done. Please review them, as I'm probably making a lot of mistakes with SGML and I can't compile it here. vacuumdb itself is not very comfortable to use when the databases have passwords, because it has to connect once for each table (I can probably make it connect only once for each database; should I?). Because of this I added a mention of PGPASSWORDFILE in the documentation, but I don't know if that is the correct place for that. Alvaro Herrera
* Add to skip list in check_gucBruce Momjian2002-08-27
|
* Comment cleanup.Bruce Momjian2002-08-27
|
* Script cleanups.Bruce Momjian2002-08-27
|
* Clean up script.Bruce Momjian2002-08-27
|
* Add check_guc utility to compare guc.c and postgresql.conf.sample.Bruce Momjian2002-08-27
|
* Fix units in postgresql.conf.Bruce Momjian2002-08-27
|
* Add units to postgresql.conf file.Bruce Momjian2002-08-26
|
* Increase WIDTH_THRESHOLD from 256 to 1K. This addresses recent observationTom Lane2002-08-26
| | | | | | that ANALYZE would not gather any stats for a CHAR(255) column. I still think a width threshold is appropriate for the reasons mentioned in the code, but we can loosen it at least.
* Modify array operations to include array's element type OID in theTom Lane2002-08-26
| | | | | | | | | | array header, and to compute sizing and alignment of array elements the same way normal tuple access operations do --- viz, using the tupmacs.h macros att_addlength and att_align. This makes the world safe for arrays of cstrings or intervals, and should make it much easier to write array-type-polymorphic functions; as examples see the cleanups of array_out and contrib/array_iterator. By Joe Conway and Tom Lane.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-07 09:17:17 +0000