- 14 10月, 2005 21 次提交
-
-
由 Bruce Momjian 提交于
regression=# select '23:59:59.9'::time(0); time ---------- 24:00:00 (1 row) This is bad because: regression=# select '24:00:00'::time(0); ERROR: date/time field value out of range: "24:00:00" The last example now works.
-
由 Tom Lane 提交于
for the PL languages and for contrib.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
etc. match the docs, which talk about "transaction identifier" not "gid" or "global transaction identifier". Steve Woodcock
-
由 Bruce Momjian 提交于
'localhost'. Improve kerberos error message.
-
由 Tom Lane 提交于
affected types of objects.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
direction of writing triggers in a procedural language, rather than C. Per discussion.
-
由 Bruce Momjian 提交于
of client_min_messages (fatal + panic) are valid and also fixes a slight issue with how psql tried to display error messages that aren't sent to the client. We often tell people to ignore errors in response to requests for things like "drop if exists", but there's no good way to completely hide this without upping client_min_messages past ERROR. When running a file like SET client_min_messages TO 'FATAL'; DROP TABLE doesntexist; with "psql -f filename" you get an error prefix of "psql:/home/username/filename:3" even though there is no error message to prefix because it isn't sent to the client. Kris Jurka
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
I'm not clear on what the double-backslash idea was intended to fix, but it breaks at least mingw GNU Make. Per report from Thomas Hallgren.
-
由 Bruce Momjian 提交于
This makes the error messages for PREPARE TRANSACTION, COMMIT PREPARED etc. match the docs, which talk about "transaction identifier" not "gid" or "global transaction identifier". Steve Woodcock
-
由 Bruce Momjian 提交于
etc. match the docs, which talk about "transaction identifier" not "gid" or "global transaction identifier". Steve Woodcock
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
applications that use FILE pointers.
-
由 Bruce Momjian 提交于
WAL and the interaction of the new full_page_writes parameter with PITR. The too-small WAL first sect1 has been merged with the one following sect1 for clarity. Some minor comments have been made in the WAL config section also. Passes SGML make and proofread for typos. Files changed: patching file doc/src/sgml/backup.sgml patching file doc/src/sgml/config.sgml patching file doc/src/sgml/wal.sgml Simon Riggs
-
由 Bruce Momjian 提交于
-
- 13 10月, 2005 15 次提交
-
-
由 Bruce Momjian 提交于
that is too fragile.
-
由 Tom Lane 提交于
syntax checking to plpgsql: check_sql_expr() wasn't being called by make_select_stmt(), so that there was no SQL syntax check for SELECT statements.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Neil Conway 提交于
-
由 Neil Conway 提交于
that is protected by a spinlock must be volatile, per recent discussion.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * Prevent PQfnumber() from lowercasing unquoted the column name > > PQfnumber() should never have been doing lowercasing, but historically > it has so we need a way to prevent it >
-
由 Tom Lane 提交于
make_restrictinfo_from_bitmapqual. The likelihood of finding duplicates seems much less than in the AND-subclause case, and the cost much higher, because OR lists with hundreds or even thousands of subclauses are not uncommon. Per discussion with Ilia Kantor and andrew@supernews.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
< * Prevent libpq's PQfnumber() from lowercasing the column name < < One idea is to lowercase all identifiers except those that are < surrounded by quotes. <
-
由 Tom Lane 提交于
the wrong buffer dirty when trying to kill a dead index entry that's on a page after the one it started on. No risk of data corruption, just inefficiency, but still a bug.
-
由 Tom Lane 提交于
protected data structures and not using a volatile pointer for same.
-
由 Tom Lane 提交于
pointers, to ensure that compilers won't rearrange accesses to occur while we're not holding the buffer header spinlock. It's probably not necessary to mark volatile in every single place in bufmgr.c, but better safe than sorry. Per trouble report from Kevin Grittner.
-
- 12 10月, 2005 4 次提交
-
-
由 Bruce Momjian 提交于
Andrew Dunstan
-
由 Bruce Momjian 提交于
< < * Add code to detect an SMP machine and handle spinlocks accordingly < from distributted.net, http://www1.distributed.net/source, < in client/common/cpucheck.cpp < < On SMP machines, it is possible that locks might be released shortly, < while on non-SMP machines, the backend should sleep so the process < holding the lock can complete and release it.
-
由 Bruce Momjian 提交于
< o %Add dumping of comments on composite type columns < o %Add dumping of comments on index columns < o Stop dumping CASCADE on DROP TYPE commands in clean mode > o %Add dumping of comments on index columns and composite type columns 604a603 > o Stop dumping CASCADE on DROP TYPE commands in clean mode
-
由 Bruce Momjian 提交于
< o %Replace crude DELETE FROM method of pg_dumpall --clean for < cleaning of roles with separate DROP commands 608a607 >
-