Tom Lane
58d8584eea
pg_dump failed on any database containing large objects,
...
because it ignored the LOs themselves but failed to ignore the indexes
on the LOs. How long has this been broken??
1999-06-03 04:01:16 +00:00
Tom Lane
f463c44fc0
Ensure consistent results when FormSortKeys fails to find
...
all the expected keys (it was returning uninitialized memory).
1999-06-03 03:17:37 +00:00
Tom Lane
9b3e2dda16
Ooops ... dllist.c can't use Assert() when it is compiled into
...
libpq ...
1999-06-03 01:28:24 +00:00
Jan Wieck
98981a9f1c
Changed "current." into "old." in rule string backparsing
...
Jan
1999-06-02 11:52:29 +00:00
Bruce Momjian
e47b93d333
The INET and CIDR types mistakenly compared 198.68.123.0/24 and
...
198.68.123.0/27 the same when indexing them.
D'Arcy
1999-06-02 03:37:15 +00:00
Thomas G. Lockhart
8593e1ff09
Make sure that only one intro is included in the integrated doc.
...
Multiple intros cause trouble since they have some section elements
(e.g. "y2k.sgml") in common leading to duplicate labels.
Include emacs formatting hints in the intro*.sgml sources.
1999-06-01 17:26:18 +00:00
Vadim B. Mikheev
bbf37e9477
typedef struct LTAG
...
{
Oid relId;
Oid dbId;
union
{
BlockNumber blkno;
TransactionId xid;
} objId;
>
> Added:
> /*
> * offnum should be part of objId.tupleId above, but would increase
> * sizeof(LOCKTAG) and so moved here; currently used by userlocks only.
> */
> OffsetNumber offnum;
uint16 lockmethod; /* needed by userlocks */
} LOCKTAG;
gmake clean required...
User locks are ready for 6.5 release...
1999-06-01 09:35:39 +00:00
Bruce Momjian
42a02c441a
forgot to attach the patch. :(
...
Vince.
1999-06-01 02:43:37 +00:00
Bruce Momjian
d2ab04ca73
commented out PgConnection& references for now. May be using them
...
later.
Vince.
1999-06-01 02:37:33 +00:00
Tom Lane
185b427284
Fix some latent bugs in dllist.c (carelessness about setting
...
all fields that should be set). Add a MoveToFront primitive to speed up
one of the hotspots in SearchSysCache.
1999-05-31 23:48:04 +00:00
Tom Lane
2a44383a2d
Clean up memory leaks in LO operations by freeing LO's private
...
memory context at transaction commit or abort.
1999-05-31 22:53:59 +00:00
Tom Lane
81ced1e037
Generate a more specific error message when an operator used
...
in an index doesn't have a restriction selectivity estimator.
1999-05-31 19:32:47 +00:00
Tom Lane
cc384fa240
Round up shmem size estimate to 1Kb boundary.
1999-05-31 18:28:52 +00:00
Tom Lane
86482e17bd
Correct serious bug in hashtable expansion routine: under the
...
right circumstances it would leave old and new bucket headers pointing to
the same list of records.
1999-05-31 17:01:52 +00:00
Bruce Momjian
7f79496aa5
NT similar file update.
1999-05-31 16:18:53 +00:00
Vadim B. Mikheev
219bb76d61
Release XactLockTable share lock immediately after this lock is acquired
...
(no sense to hold it) or we'll be out of lock entries.
Great thanks to Hiroshi Inoue.
1999-05-31 01:48:13 +00:00
Tom Lane
ca08ce28e8
Clean up uninitialized-variable warning from egcs.
...
(Curious that gcc doesn't complain about this code...).
1999-05-30 15:32:45 +00:00
Tom Lane
3257b0e592
egcs thinks omitting the return type in a function declaration
...
is poor coding style. I agree.
1999-05-30 15:22:34 +00:00
Tom Lane
d4d297af3c
Replace static rcsid[] strings by IDENTIFICATION comments in
...
file headers, to conform to established Postgres coding style and avoid
warnings from gcc.
1999-05-30 15:17:58 +00:00
Tom Lane
6687bcb558
configure.in forgot to do AC_LANG_C to reselect C-based tests
...
after checking for presence of C++ compiler. Odd we hadn't seen any
reports of problems before...
1999-05-30 00:06:44 +00:00
Tom Lane
6f979c1541
Turns out that configure's test for HPUXMATHLIB didn't work
...
when used with egcs --- now it does.
1999-05-29 16:26:42 +00:00
Vadim B. Mikheev
df9e539ea2
1. Run all pg_dump queries in single serializable transaction.
...
2. Get rid of locking when updating statistics in vacuum.
3. Use QuerySnapshot in COPY TO and call SetQuerySnashot
in main tcop loop before FETCH and COPY TO.
1999-05-29 10:25:33 +00:00
Vadim B. Mikheev
bbbc211ed1
Fix xid table sizing.
1999-05-29 06:14:43 +00:00
Tom Lane
dfefad7db0
Missing semicolons in non-HAS_TEST_AND_SET code paths :-(
1999-05-29 03:58:43 +00:00
Tom Lane
1bdd7c68c0
Avoid redundant SysCache searches in coerce_type, for another
...
few percent speedup in INSERT...
1999-05-29 03:17:20 +00:00
Tom Lane
b325dab67a
new_relation_targetlist used to cause about 8 separate (and
...
redundant) SearchSysCache searches per table column in an INSERT, which
accounted for a good percentage of the CPU time for INSERT ... VALUES().
Now it only does two searches in the typical case.
1999-05-29 01:48:06 +00:00
Tom Lane
ce2586dbc9
Clean up inefficient and just plain bad code in some hot-spot
...
cache access routines.
1999-05-29 01:45:21 +00:00
Tom Lane
dc6d404959
Repair performance problem in SI segment manipulations: iterating
...
through MAXBACKENDS array entries used to be fine when MAXBACKENDS = 64.
It's not so cool with MAXBACKENDS = 1024 (or more!), especially not in a
frequently-used routine like SIDelExpiredDataEntries. Repair by making
procState array size be the soft MaxBackends limit rather than the hard
limit, and by converting SIGetProcStateLimit() to a macro.
1999-05-28 17:03:31 +00:00
Bruce Momjian
33c6d6099d
Clean up mention of gmake vs. make.
1999-05-28 14:24:24 +00:00
Bruce Momjian
b344b513c7
Update pygresql version stamp.
1999-05-28 04:54:34 +00:00
Tom Lane
f0ae1e8d10
When closure of the backend connection is detected during pqFlush,
...
do the right thing: look for a NOTICE message from the backend before we
close our side of the socket. 6.4 libpq did not reliably print the backend's
hara-kiri message, 'The Postmaster has informed me ...', because it only
did the right thing if connection closure was detected during a read
attempt instead of a write attempt.
1999-05-28 01:54:53 +00:00
Bruce Momjian
615e77ede2
Make pg_dump dump ACL's by default, print warning on use of -z, and add
...
new -x option to skip acl dump.
1999-05-27 16:29:05 +00:00
Thomas G. Lockhart
e53c51280b
More info is in sgml and html docs so this is now obsolete.
1999-05-27 16:06:33 +00:00
Thomas G. Lockhart
39c02dfefa
FAQs contributed for this release.
1999-05-27 16:05:38 +00:00
Thomas G. Lockhart
5b1b477cca
Markup fixes.
1999-05-27 15:49:15 +00:00
Thomas G. Lockhart
b805230906
Markup fixes.
...
Update for v6.5 release.
1999-05-27 15:49:08 +00:00
Thomas G. Lockhart
7d831b5379
Significant updates from Vince Vielhaber.
1999-05-27 15:48:14 +00:00
Thomas G. Lockhart
b04b01638b
Remove disclaimer about exact numeric types. They work now!
1999-05-27 15:47:28 +00:00
Thomas G. Lockhart
8a3c7535c5
Refresh FreeBSD info.
1999-05-27 15:46:22 +00:00
Thomas G. Lockhart
d6efbf1956
Significant update from Vince Vielhaber.
1999-05-27 15:44:54 +00:00
Bruce Momjian
874957a32a
Update release notes for 6.5.
1999-05-27 15:13:43 +00:00
Bruce Momjian
5fec534f4b
Clean up release sgml file.
1999-05-27 15:05:57 +00:00
Bruce Momjian
781a1eb99a
I am not sure if libpq++ will compile with non g++ compilers,
...
but the Makefile does break non g++.
<<mak.patch>>
Andreas
1999-05-27 14:28:40 +00:00
Bruce Momjian
0d5f7ce11c
Fix for crypt memory leak, from James Thompson
1999-05-27 04:09:45 +00:00
Tom Lane
7c8beefd5e
Patch from Andreas: when CREATE TABLE is followed by CREATE INDEX
...
before any tuples are loaded, preserve the default '1000 tuples' table
size estimate.
1999-05-26 22:57:39 +00:00
Tom Lane
8eb18d874e
Fix pg_dump to use the same maximum-query-size constant as
...
the backend does. Remove unnecessary limitation on field size in
dumpClasses_dumpData (ie, -d or -D case).
1999-05-26 21:51:13 +00:00
Bruce Momjian
26fb87d37e
Fix compile of plpgsql by adding 'extern int yylineno.'
1999-05-26 20:55:06 +00:00
Bruce Momjian
bf09f8aa43
Display numeric precision on \d.
1999-05-26 20:08:06 +00:00
Bruce Momjian
e7528612d8
Allow GROUPs to be dumped properly.
1999-05-26 19:45:53 +00:00
Thomas G. Lockhart
9474dd7ed6
Add chapters on CVS access, MVCC, SQL theory to the docs.
...
Add an appendix with more details on date/time attributes and handling.
Update most references to Postgres version numbers to 6.5,
*except* for the porting list which will require a report
from a successful installation to be updated.
1999-05-26 17:30:30 +00:00