- 03 Sep, 2003 5 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Tom Lane authored
-
Tom Lane authored
From Karel Zak.
-
- 02 Sep, 2003 6 commits
-
-
Tom Lane authored
killed items; just skip to the next item immediately. Only check for key equality when we reach a non-killed item or the end of the index page. This saves key comparisons when there are lots of killed items, as for example in a heavily-updated table that's not been vacuumed lately. Seems to be a win for pgbench anyway.
-
Peter Eisentraut authored
-
Tom Lane authored
config file if it exists. This was already discussed as being a good idea, and now seems the cleanest way to deal with initdb-time failures on machines with small SHMMAX. (The submitted patches instead modified initdb.sh to pass the correct sizing parameters, but that would still leave standalone backends prone to failure later. An admin who needs to use a standalone backend has enough trouble already, he shouldn't have to manually configure its shmem settings...)
-
Tom Lane authored
layout; therefore, this change forces REINDEX of hash indexes (though not a full initdb). Widen hashm_ntuples to double so that hash space management doesn't get confused by more than 4G entries; enlarge the allowed number of free-space-bitmap pages; replace the useless bshift field with a useful bmshift field; eliminate 4 bytes of wasted space in the per-page special area.
-
Tom Lane authored
-
Tom Lane authored
scheme. A pleasant side effect is that it is *much* faster when deleting a large fraction of the indexed tuples, because of elimination of redundant hash_step activity induced by hash_adjscans. Various other continuing code cleanup.
-
- 01 Sep, 2003 7 commits
-
-
Peter Eisentraut authored
libpq, talking to an old server, should assume SQL_ASCII as the default client encoding, because that is what the server will actually use (not the server encoding).
-
Peter Eisentraut authored
unneeded configure work.
-
Tom Lane authored
yet). Fix a couple of bugs that would only appear if multiple bitmap pages are used, including a buffer reference leak and incorrect computation of bit indexes. Get rid of 'overflow address' concept, which accomplished nothing except obfuscating the code and creating a risk of failure due to limited range of offset field. Rename some misleadingly-named fields and routines, and improve documentation.
-
Tom Lane authored
explanation of the remarkably confusing page addressing scheme. The file also includes my planned-but-not-yet-implemented revision of the hash index locking scheme.
-
Bruce Momjian authored
-
Michael Meskes authored
-
Bruce Momjian authored
-
- 31 Aug, 2003 3 commits
-
-
Peter Eisentraut authored
-
Peter Eisentraut authored
-
Peter Eisentraut authored
-
- 30 Aug, 2003 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
- 28 Aug, 2003 5 commits
-
-
Tom Lane authored
slight resemblance to their actual behavior.
-
Tom Lane authored
different object types. Fix, and centralize logic to try to prevent the same mistake in future.
-
Tom Lane authored
rather than relying on OID order of pg_constraint entries. Per gripe from Greg Stark.
-
Tom Lane authored
-
Teodor Sigaev authored
-
- 27 Aug, 2003 7 commits
-
-
Tom Lane authored
SQLSTATE error codes required by SQL99 (invalid format, datetime field overflow, interval field overflow, invalid time zone displacement value). Also emit a HINT about DateStyle in cases where it seems appropriate. Per recent gripes.
-
Peter Eisentraut authored
this variable on the command line.
-
Peter Eisentraut authored
-
Tom Lane authored
-
-
PostgreSQL Daemon authored
update to beta2
-
Peter Eisentraut authored
-
- 26 Aug, 2003 5 commits
-
-
Tom Lane authored
only scan plans. Per observation from Rod Taylor.
-
Bruce Momjian authored
-
Tom Lane authored
lumping them into ERRCODE_UNDEFINED_OBJECT/ERRCODE_DUPLICATE_OBJECT. This seems reasonable since 'object' was meant to refer to 'object in the database' and a file is outside the database. Per request from Dave Cramer.
-
Bruce Momjian authored
that HISTSIZE might take effect from my .psqlrc Andriy Tkachuk
-
Bruce Momjian authored
now all that is tested is Rod Taylor's recent addition to allow this syntax: UPDATE ... SET <col> = DEFAULT; If anyone else would like to add more UPDATE tests, go ahead -- I just wanted to write a test for the above functionality, and couldn't see an existing test that it would be appropriate to add to. Neil Conway
-