| Commit message (Collapse) | Author | Age |
|
|
|
| |
for SERIAL column's constraint, but forgot to increase space palloc'd...
|
| |
|
|
|
|
| |
ports collection ...
|
| |
|
| |
|
| |
|
|
|
|
| |
for GEQO ...
|
|
|
|
|
| |
is evaluated. This bounds memory usage to something reasonable even
when many tables are being joined.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
reasonable plans again. Still eats memory like there's no tomorrow,
however :-(.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
segments, and my indexes had 3(Yes, it DOES work!).
DROP TABLE removed ALL segments from the table, but only the main index
segment.
So it looks like removing the table itself is using mdunlink in md.c,
while removing indexes uses FileNameUnlink() which only unlinks 1 file.
As far as I can tell, calling FileNameUnlink() and mdunlink() is basically
the same, except mdunlink() deletes any extra segments.
I've done some testing and it seems to work. It also passes regression
tests(except float8, geometry and rules, but that's normal).
If this patch is right, this fixes all known multi-segment problems on
Linux.
Ole Gjerde
|
|
|
|
|
|
|
| |
These are my last changes to lmgr fixing deadlock handling.
Please apply them to cvs...
Vadim
|
|
|
|
|
|
| |
SERIAL data type DEFAULT clause.
This fixes a problem finding the sequence name when mixed case table names
are involved.
|
|
|
|
| |
compiler warnings about an unused variable.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
lists are now plain old garden-variety Lists, allocated with palloc,
rather than specialized expansible-array data allocated with malloc.
This substantially simplifies their handling and eliminates several
sources of memory leakage.
Several basic types of erroneous queries (syntax error, attempt to
insert a duplicate key into a unique index) now demonstrably leak
zero bytes per query.
|
| |
|
|
|
|
|
|
| |
pg_rules to rules regression test.
Jan
|
|
|
|
|
|
|
|
| |
selected.
Disabled ability of defining DISTINCT or ORDER BY on views.
Jan
|
|
|
|
|
|
|
| |
in Resdom and GroupClause so changing of resno's doesn't confuse
the grouping any more.
Jan
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The
offending code
has been removed, the action is now always dependent :-)
I suggest the following patch, to finally make trigger regression happy
again:
<<refint1.patch>>
After that you can remove the following from TODO:
Remove ERROR: check_primary_key: even number of arguments should be
specified
Trigger regression test fails
Andreas
|
|
|
|
|
|
|
|
|
|
| |
and lock syntax as fully parsed tokens.
Two keywords for isolation are non-reserved SQL92
(COMMITTED, SERIALIZABLE).
All other new keywords are non-reserved Postgres (not SQL92)
(ACCESS, EXCLUSIVE, MODE, SHARE).
Add syntax to allow CREATE [GLOBAL|LOCAL] TEMPORARY TABLE, throwing an
error if GLOBAL is specified.
|
|
|
|
|
|
|
| |
constraints. Reported by Tom Lane.
Now, check for duplicate indices and retain the one which is a primary-key.
Adjust elog NOTICE messages to surround table and column names with single
quotes.
|
| |
|
|
|
|
|
|
| |
the obvious conversion.
Define a new pattern "decimal" which is non-exponential floating point
for use with numeric() and decimal() types.
|
|
|
|
|
|
|
|
|
| |
-d4 now prints compressed trees from nodeToString()
-d5 prints pretty trees via nodeDisplay()
new pg_options: pretty_plan, pretty_parse, pretty_rewritten
Jan
|
| |
|
|
|
|
| |
Jan
|
| |
|
| |
|
| |
|
|
|
|
| |
real affect now.
|
|
|
|
| |
on queries involving UNION, EXCEPT, INTERSECT.
|
|
|
|
|
|
| |
cause troubles. See
Message-Id: <199905090312.MAA00466@ext16.sra.co.jp>
for more details.
|
|
|
|
| |
Fixed by Hiroshi.
|
|
|
|
| |
fopen(), instead of going through fd.c ... naughty naughty.
|
|
|
|
| |
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.
|
|
|
|
| |
that led to CASE expressions not working very well in joined queries.
|
|
|
|
|
|
| |
meaning that this failed:
select proname,typname,prosrc from pg_proc,pg_type
where proname = 'float8' and pg_proc.proargtypes[0] = pg_type.oid;
|
|
|
|
|
|
|
|
|
|
| |
about certain to fail anytime it decided the relation to be hashed was
too big to fit in memory --- the code for 'batching' a series of hashjoins
had multiple errors. I've fixed the easier problems. A remaining big
problem is that you can get 'hashtable out of memory' if the code's
guesstimate about how much overflow space it will need turns out wrong.
That will require much more extensive revisions to fix, so I'm committing
these fixes now before I start on that problem.
|
|
|
|
|
|
|
|
|
|
| |
arrayfuncs.patch fixes a small bug in my previous patches for
arrays
array-regress.patch adds _bpchar and _varchar to regression tests
--
Massimo Dal Zotto
|
| |
|
| |
|
|
|
|
|
| |
Original code used float8out(), but the resulting exponential notation
was not handled (e.g. '3E9' was decoded as '3').
|
|
|
|
|
| |
nodes with HAVING qualifier of upper plan. Have not seen any failures,
just being a little bit paranoid...
|
|
|
|
| |
gcc quite so unhappy.
|