- Apr 11, 1998
-
-
Marc G. Fournier authored
variable name *blush* *grin*
-
- Apr 10, 1998
-
-
Marc G. Fournier authored
-
Marc G. Fournier authored
-
- Feb 26, 1998
-
-
Bruce Momjian authored
-
- Jan 15, 1998
-
-
PostgreSQL Daemon authored
Patch by: wieck@sapserv.debis.de (Jan Wieck) One of the design rules of PostgreSQL is extensibility. And to follow this rule means (at least for me) that there should not only be a builtin PL. Instead I would prefer a defined interface for PL implemetations.
-
- Jan 07, 1998
-
-
Bruce Momjian authored
-
- Jan 05, 1998
-
-
Bruce Momjian authored
-
- Oct 22, 1997
-
-
Vadim B. Mikheev authored
-
- Sep 08, 1997
-
-
Bruce Momjian authored
-
Bruce Momjian authored
Another PGINDENT run that changes variable indenting and case label indenting. Also static variable indenting.
-
- Sep 07, 1997
-
-
Bruce Momjian authored
-
- Aug 19, 1997
-
-
Bruce Momjian authored
-
- Aug 13, 1997
-
-
Bruce Momjian authored
-
- Jun 10, 1997
-
-
Vadim B. Mikheev authored
-
- May 30, 1997
-
-
Vadim B. Mikheev authored
-
- May 05, 1997
-
-
Vadim B. Mikheev authored
when btree used in innerscan with run-time key which value passed by pointer. Fix: keys ordering stuff moved to _bt_first(). Pointed by Thomas Lockhart.
-
- Apr 24, 1997
-
-
Vadim B. Mikheev authored
-
- Apr 16, 1997
-
-
Vadim B. Mikheev authored
index tuple (logical position within A LEVEL). bti_oid & bti_dummy taken off from BTItemData. 2. Fix for multi-column indices (nbtsearch.c): _bt_binsrch() - for searches on internal pages having keysize < number of attrs we point at the last item < the scankey, not at the first item = the scankey; _bt_moveright() - if keysize < number of attrs we compare scankey with _last_ item on current page to decide should we move right or not.
-
- Mar 24, 1997
-
-
Vadim B. Mikheev authored
Actually required by multi-column indices support. We still don't use btree for 'A is (not) null', but now btree keep items with NULL attrs using single rule for placing/finding items on pages: NULLs greater NOT_NULLs and NULL = NULL. + Bulkload code (nbtsort.c) support for multi-column indices building and NULLs. + Fix for btendscan()->pfree(scanopaque) from Chris Dunlop.
-
- Mar 18, 1997
-
-
Marc G. Fournier authored
-
- Feb 18, 1997
-
-
Bruce Momjian authored
-
- Jan 05, 1997
-
-
Vadim B. Mikheev authored
buffer leak.
-
- Dec 15, 1996
-
-
Bryan Henderson authored
-
- Dec 06, 1996
-
-
Vadim B. Mikheev authored
(old _bt_compare always returned >= 0 while comparing with P_HIKEY on root page - it breaks root page when _bt_insertonpg tries insert new minimal key into root page). 2. Fixed bug concerns "empty" pages: non-rightmost pages with only P_HIKEY present on it. Such pages appear after vacuum.
-
- Nov 21, 1996
-
-
Vadim B. Mikheev authored
memory allocation for ItemPointerData of heap' tuple is useless because of FormRetrieveIndexResult makes neccessary palloc.
-
- Nov 13, 1996
-
-
Marc G. Fournier authored
Changes: * Unique index capability works using the syntax 'create unique index'. * Duplicate OID's in the system tables are removed. I put little scripts called 'duplicate_oids' and 'find_oid' in include/catalog that help to find and remove duplicate OID's. I also moved 'unused_oids' from backend/catalog to include/catalog, since it has to be in the same directory as the include files in order to work. * The backend tries converting the name of a function or aggregate to all lowercase if the original name given doesn't work (mostly for compatibility with ODBC). * You can 'SELECT NULL' to your heart's content. * I put my _bt_updateitem fix in instead, which uses _bt_insertonpg so that even if the new key is so big that the page has to be split, everything still works. * All literal references to system catalog OID's have been replaced with references to define'd constants from the catalog header files. * I added a couple of node copy functions. I think this was a preliminary attempt to get rules to work.
-
- Nov 05, 1996
-
-
Marc G. Fournier authored
-
- Nov 03, 1996
-
-
Marc G. Fournier authored
-
Marc G. Fournier authored
cleaning up behind myself before *yawn* bed :)
-
- Oct 30, 1996
-
-
Marc G. Fournier authored
I found another bug in btree index. Looking at the code it seems that NULL keys are never used to build or scan a btree index (see the explain commands in the example). However this is not the case when a null key is retrieved in an outer loop of a join select and used in an index scan of an inner loop. This bug causes at least three kinds of problems: 1) the backend crashes when it tries to compare a text string with a null. 2) it is not possible to find tuples with null keys in a join. 3) null is considered equal to 0 when the datum is passed by value, see the last query. Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
-
- Oct 23, 1996
-
-
Marc G. Fournier authored
-
- Oct 20, 1996
-
-
Marc G. Fournier authored
-
- Jul 30, 1996
-
-
Marc G. Fournier authored
> INDEXED searches in some cases DO NOT WORK. > Although simple search expressions (i.e. with a constant value on > the right side of an operator) work, performing a join (by putting > a field of some other table on the right side of an operator) produces > empty output. > WITHOUT indices, everything works fine. > submitted by: "Vadim B. Mikheev" <root@ais.sable.krasnoyarsk.su>
-
- Jul 09, 1996
-