| Commit message (Collapse) | Author | Age |
|
|
|
| |
code, instead of not-very-bulletproof stuff they had before.
|
|
|
|
|
|
|
|
|
| |
files to be closed automatically at transaction abort or commit, should
they still be open. Also close any still-open stdio files allocated with
AllocateFile at abort/commit. This should eliminate problems with leakage
of file descriptors after an error. Also, put in some primitive buffered-IO
support so that psort.c can use virtual files without severe performance
penalties.
|
|
|
|
| |
Get rid of Extend lock mode.
|
|
|
|
| |
FATAL 1:btree: BTP_CHAIN flag was expected
|
|
|
|
| |
should be faster.
|
|
|
|
| |
but I think it's OK now...
|
|
|
|
|
|
| |
can be generated in a buffer and then sent to the frontend in a single
libpq call. This solves problems with NOTICE and ERROR messages generated
in the middle of a data message or COPY OUT operation.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
indexes.
1. Index Scan using plural indexids never scan backward
as to the order of indexids.
2. The cursor using Index scan is not usable after moving
past the end.
This patch solves above bugs.
Moreover the change of _bt_first() would be useful to extend
ORDER BY patch by Jan Wieck for all descending order cases.
Hiroshi Inoue
|
|
|
|
|
|
|
| |
/*
* Have to check is inserted heap tuple deleted one
* (i.e. just moved to another place by vacuum)!
*/
|
| |
|
|
|
|
|
|
|
| |
2. Much faster btree tuples deletion in the case when first on page
index tuple is deleted (no movement to the left page(s)).
3. Remember blkno of new root page in BTPageOpaque of
left/right siblings when root page is splitted.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I would like some feedback on what the hash function for the int8 hash
function
in the ./backend/access/hash/hashfunc.c should return.
Also, could someone (maybe Tomas Lockhart?) look-over the patch and make
sure
the system table entries are correct? I've tried to research them as
much as I
could, but some of them are still not clear to me.
Thanks,
-Ryan
|
|
|
|
|
|
| |
Ok. I made patches replacing all of "#if FALSE" or "#if 0" to "#ifdef
NOT_USED" for current. I have tested these patches in that the
postgres binaries are identical.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
result, too ... another little bit of speed for SELECT.
|
|
|
|
|
| |
only once per SELECT, not once per tuple. 10% here, 10% there,
pretty soon you're talking about real speedups ...
|
|
|
|
| |
seems to have improved speed of routine by 5% or so ...
|
|
|
|
| |
but useful speedup.
|
|
|
|
|
|
| |
so that fetching an attribute value needs only one SearchSysCacheTuple call
instead of two redundant searches. This speeds up a large SELECT by about
ten percent, and probably will help GROUP BY and SELECT DISTINCT too.
|
|
|
|
| |
gcc complained about ambiguities.
|
| |
|
|
|
|
|
| |
LOCK TABLE IN ... MODE
...implemented
|
| |
|
|
|
|
| |
New code for locking buffer' context.
|
| |
|
|
|
|
|
|
| |
Switch sprintf() to snprintf()
Remove any/all #if 0 -or- #ifdef NOT_USED -or- #ifdef FALSE sections of
code
|
|
|
|
|
|
|
|
|
|
| |
enabled PostgreSQL 6.4.
o binary cursor does not work
o pg_dumpall produces incorrect create database statemnt
Tatsuo Ishii
t-ishii@sra.co.jp
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
and possibly other problems. Minor changes in xact.c and postgres.c's
main loop to support new handling of async NOTIFY.
|
|
|
|
|
| |
system. Finally got tired of looking at the compiler warning messages.
BSHIFT isn't all that useful, so I just took out the macro.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for against a just updated CVS tree. It contains
Partial new rewrite system that handles subselects, view
aggregate columns, insert into select from view, updates
with set col = view-value and select rules restriction to
view definition.
Updates for rule/view backparsing utility functions to
handle subselects correct.
New system views pg_tables and pg_indexes (where you can
see the complete index definition in the latter one).
Enabling array references on query parameters.
Bugfix for functional index.
Little changes to system views pg_rules and pg_views.
The rule system isn't a release-stopper any longer.
But another stopper is that I don't know if the latest
changes to PL/pgSQL (not already in CVS) made it compile on
AIX. Still wait for some response from Dave.
Jan
|
| |
|
|
|
|
| |
just two macros.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
After some playing with gdb I found that in printtup() there is a non null
attribute with typeinfo->attrs[i]->atttypid = 0 (invalid oid). Unfortunately
attibutes with invalid type are neither printed nor marked as null, and this
explains why psql doesn't get all the expected data.
So I made this patch to printtup():
|
| |
|