aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
* 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.
* Add Bob Devine's name to the optimizer README.Bruce Momjian2002-08-25
|
* Clean up comments to be careful about the distinction between variable-Tom Lane2002-08-25
| | | | | | | | | | width types and varlena types, since with the introduction of CSTRING as a more-or-less-real type, these concepts aren't identical. I've tried to use varlena consistently to denote datatypes with typlen = -1, ie, they have a length word and are potentially TOASTable; while the term variable width covers both varlena and cstring (and, perhaps, someday other types with other rules for computing the actual width). No code changes in this commit except for renaming a couple macros.
* The cstring datatype can now be copied, passed around, etc. The typlenTom Lane2002-08-24
| | | | | | | value '-2' is used to indicate a variable-width type whose width is computed as strlen(datum)+1. Everything that looks at typlen is updated except for array support, which Joe Conway is working on; at the moment it wouldn't work to try to create an array of cstring.
* Further cleanup around the edges of OPAQUE/pseudotype changes. CorrectTom Lane2002-08-23
| | | | | the declarations of some index access method support functions. Support SQL functions returning VOID.
* Code review for recent TRUNCATE changes. Tighten relation-kind check,Tom Lane2002-08-22
| | | | | | tighten foreign-key check (a self-reference should not prevent TRUNCATE), improve error message, cause a relation's TOAST table to be truncated along with the relation.
* Commit updated repeat() patch, from Neil ConwayBruce Momjian2002-08-22
|
* This patch should fix the problem. Doesn't include my previous patchBruce Momjian2002-08-22
| | | | | | | | | | | | | | | for repeat(). Again, somewhat off-the-cuff, so I might have missed something... test=# select lpad('xxxxx',1431655765,'yyyyyyyyyyyyyyyy'); ERROR: Requested length too large test=# select rpad('xxxxx',1431655765,'yyyyyyyyyyyyyyyy'); ERROR: Requested length too large (That's on a Unicode DB, haven't tested other encodings but AFAICT this fix should still work.) Neil Conway
* repeat() fix:Bruce Momjian2002-08-22
| | | | | | | | | | | | | | | | > Neil Conway <neilc@samurai.com> writes: > > + /* Check for integer overflow */ > > + if (tlen / slen != count) > > + elog(ERROR, "Requested buffer is too large."); > > What about slen == 0? Good point -- that wouldn't cause incorrect results or a security problem, but it would reject input that we should really accept. Revised patch is attached. Neil Conway
* # Disallow TRUNCATE on tables that are involved in referentialBruce Momjian2002-08-22
| | | | | | | | | | | | | constraints The issue with finding and removing foreign key constraints is no longer an issue, so please apply the attached. It does NOT check for rules or on delete triggers (old style foreign keys) as those are difficult to deal with (remove, truncate, re-add). Rod Taylor
* As suggested by Tom, this patch restricts the right-hand argument ofBruce Momjian2002-08-22
| | | | | | | | | | | bytealike to TEXT. This leaves like_escape_bytea() without anything to do, but I left it in place in anticipation of the eventual bytea pattern selectivity functions. If there is agreement that this would be the best long term solution, I'll take it as a TODO for 7.4. Joe Conway
* Add:Bruce Momjian2002-08-22
| | | | | | | | | | | replace(string, from, to) -- replaces all occurrences of "from" in "string" to "to" split(string, fldsep, column) -- splits "string" on "fldsep" and returns "column" number piece to_hex(int32_num) & to_hex(int64_num) -- takes integer number and returns as hex string Joe Conway
* Remove erroneous character from Makefile due to editor error.Bruce Momjian2002-08-22
|
* Add a bunch of pseudo-types to replace the behavior formerly associatedTom Lane2002-08-22
| | | | | | with OPAQUE, as per recent pghackers discussion. I still want to do some more work on the 'cstring' pseudo-type, but I'm going to commit the bulk of the changes now before the tree starts shifting under me ...
* Changes made so new conversion Makefiles will build out of the source tree.Bruce Momjian2002-08-21
|
* Move PO files into subdirectories separate from the source code.Peter Eisentraut2002-08-21
|
* Increase buffer size in cash_words(). Pure paranoia; I don't think theTom Lane2002-08-20
| | | | | code is broken, but any small change in the output format might overrun the buffer with the old size.
* Allow pg_statistics to be reset by calling pg_stat_reset().Bruce Momjian2002-08-20
| | | | Christopher Kings-Lynne
* Add current_database().Bruce Momjian2002-08-20
| | | | | | | | | | | | | | | > Quick system function to pull out the current database. > > I've used this a number of times to allow stored procedures to find out > where they are. Especially useful for those that do logging or hit a > remote server. > > It's called current_database() to match with current_user(). It's also a necessity for an informational schema. The catalog (database) name is required in a number of places. Rod Taylor
* Fix pg_dump to dump serial columns as serials. Per pghackers discussion,Tom Lane2002-08-19
| | | | | cause SERIAL column declaration not to imply UNIQUE, so that this can be done without creating an extra index.
* Remove Ident nodetype in favor of using String nodes; this fixes someTom Lane2002-08-19
| | | | | | | | | | latent wrong-struct-type bugs and makes the coding style more uniform, since the majority of places working with lists of column names were already using Strings not Idents. While at it, remove vestigial support for Stream node type, and otherwise-unreferenced nodes.h entries for T_TupleCount and T_BaseNode. NB: full recompile is recommended due to changes of Node type numbers. This shouldn't force an initdb though.
* Fix bug in pg_convert() per report from MaC.Yui.Tatsuo Ishii2002-08-19
| | | | It pfree() wrong pointer.
* Clean up leftover bugs from recent COPY feature patch --- missedTom Lane2002-08-19
| | | | required changes to copyfuncs/equalfuncs.
* Add missing copyfuncs/equalfuncs entries, including T_Null which hasTom Lane2002-08-19
| | | | | been missing forever; surprising it wasn't noticed before. The other additions are, um, sloppiness in certain recent feature additions.
* Remove optimization whereby parser would make only one sort-list entryTom Lane2002-08-18
| | | | | | | | when two equal() targetlist items were to be added to an ORDER BY or DISTINCT list. Although indeed this would make sorting fractionally faster by sometimes saving a comparison, it confuses the heck out of later stages of processing, because it makes it look like the user wrote DISTINCT ON rather than DISTINCT. Bug reported by joe@piscitella.com.
* Make CREATE CONSTRAINT TRIGGER check for REFERENCES privilege on bothPeter Eisentraut2002-08-18
| | | | master and slave tables.
* Make pg_dump output more portable and more pleasing to look at.Peter Eisentraut2002-08-18
| | | | | | | | | | | | | | | | | The -n and -N options were removed. Quoting is now smart enough to supply quotes if and only if necessary. Numerical types are now printed without quotes, except in cases of special values such as NaN. Boolean values printed as true and false. Most string literals now do not escape whitespace characters (newlines, etc.) for portability. SET SESSION AUTHORIZATION argument is a string literal, to follow SQL. Made commands output by pg_dump use consistent spacing and indentation.
* Code review for 'at character n' patch --- point at proper end ofTom Lane2002-08-18
| | | | a token scanned by multiple lex rules.
* Add db-local user names, per discussion on hackers.Bruce Momjian2002-08-18
|
* Reverse out XLogDir/-X write-ahead log handling, per discussion.Bruce Momjian2002-08-17
| | | | Original patch from Thomas.
* Add lock file.Bruce Momjian2002-08-17
|
* In that case, attached is a patch which locates the beginning of theBruce Momjian2002-08-17
| | | | | | | | | | | | | | | offending token more efficiently (per your suggestion of using scanbuf). The new patch does the same as before: template1=# select * frum pg_class; ERROR: parser: parse error at or near "frum" at character 10 It also implement's Tom's suggestion: template1=# select * from pg_class where\g ERROR: parse: parse error at end of input Gavin Sherry
* [ Newest version of patch applied.]Bruce Momjian2002-08-17
| | | | | | | | | | | | | | | | | | This patch is an updated version of the lock listing patch. I've made the following changes: - write documentation - wrap the SRF in a view called 'pg_locks': all user-level access should be done through this view - re-diff against latest CVS One thing I chose not to do is adapt the SRF to use the anonymous composite type code from Joe Conway. I'll probably do that eventually, but I'm not really convinced it's a significantly cleaner way to bootstrap SRF builtins than the method this patch uses (of course, it has other uses...) Neil Conway
* Improve documentation of trigger firing queue handling, cleanup.Bruce Momjian2002-08-17
| | | | Neil Conway
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-02 17:05:57 +0000