| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
Made ecpg parser use backend provided keyword list.
Changed whenever test so exit value is 0.
|
|
|
|
| |
modify the passed string.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to go beoynd 10MB, as demonstrated by Gavin Sharry's example of dropping a
schema with ~25000 objects. The really bogus thing about the limit was that
it was enforced when a state file file was read in, not when it was written,
so you would end up with a prepared transaction that you can't commit or
abort, and the only recourse was to shut down the server and remove the file
by hand.
Raise the limit to MaxAllocSize, and enforce it also when a state file is
written. We could've removed the limit altogether, but reading in a file
larger than MaxAllocSize would fail anyway because we read it into a
palloc'd buffer.
Backpatch down to 8.1, where 2PC and this issue was introduced.
|
|
|
|
| |
Euler Taveira de Oliveira
|
|
|
|
|
| |
example from Rod Taylor. On reflection the correct test here is for any
polymorphic type, not specifically ANYARRAY as in the original coding.
|
|
|
|
|
| |
found to have been made necessary by our skipping tty detection on Windows. Now
that we are doing tty detection on Windows the kluge is unnecessary and wrong.
|
|
|
|
| |
Per buildfarm results.
|
|
|
|
| |
that platform.
|
| |
|
| |
|
| |
|
|
|
|
| |
Per buildfarm results.
|
|
|
|
| |
exits with nonzero status. The Windows part of this is untested ...
|
|
|
|
|
| |
spoonbill, though one wonders why it didn't misbehave everywhere.
In passing remove some unnecessary modulo calculations.
|
|
|
|
|
|
|
|
| |
Formerly, the default value of wal_sync_method was determined inside xlog.c,
but now it is determined inside guc.c. guc.c was reading xlogdefs.h
without having read <fcntl.h>, leading to wrong determination of
DEFAULT_SYNC_METHOD. Obviously xlogdefs.h needs to include <fcntl.h>
for itself to ensure stable results.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This particular batch was just for *.c and *.h file.
The changes were made with the following 2 commands:
find . \( \( -name 'libstemmer' -o -name 'expected' -o -name 'ppport.h' \) -prune \) -o \( -name '*.[ch]' \) \( -exec grep -q '\$PostgreSQL' {} \; -o -print \) | while read file ; do head -n 1 < $file | grep -q '^/\*' && echo $file; done | xargs -l sed -i -e '1s/^\// /' -e '1i/*\n * $PostgreSQL:$ \n *'
find . \( \( -name 'libstemmer' -o -name 'expected' -o -name 'ppport.h' \) -prune \) -o \( -name '*.[ch]' \) \( -exec grep -q '\$PostgreSQL' {} \; -o -print \) | xargs -l sed -i -e '1i/*\n * $PostgreSQL:$ \n */'
|
|
|
|
|
| |
sequence. This seems an obvious extension to the recent patch, and it
makes the code noticeably cleaner and more orthogonal.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sequence to be reset to its original starting value. This requires adding the
original start value to the set of parameters (columns) of a sequence object,
which is a user-visible change with potential compatibility implications;
it also forces initdb.
Also add hopefully-SQL-compatible RESTART/CONTINUE IDENTITY options to
TRUNCATE TABLE. RESTART IDENTITY executes ALTER SEQUENCE RESTART for all
sequences "owned by" any of the truncated relations. CONTINUE IDENTITY is
a no-op option.
Zoltan Boszormenyi
|
| |
|
| |
|
|
|
|
|
| |
on Apple's gcc and not my other machines, but still it seems worth
getting rid of.)
|
|
|
|
|
|
|
|
|
| |
should always succeed, but in the likely event of a failure we would
previously fall through *without locking* - the new code will exit(1).
Printing the error message on stderr will not work for all applications, but
it's better than nothing at all - and our API doesn't provide a way to return
the error to the caller.
|
|
|
|
|
|
|
|
|
|
| |
Add a few "help" entries.
Move \g help entry into "General".
Update psql version mismatch warning text.
Joshua D. Drake
|
|
|
|
|
| |
detection for wrapped lines or lines with newlines that need pager to
display.
|
|
|
|
|
|
| |
prefix matching using this facility.
Teodor Sigaev and Oleg Bartunov
|
|
|
|
| |
Author: Euler Taveira de Oliveira <euler@timbira.com>
|
|
|
|
| |
while building a GIN index.
|
|
|
|
| |
Pavel Stehule
|
|
|
|
|
| |
CoerceViaIO nodes. This improves the ability of the planner to deal with
cases where the node input is a constant. Per bug #4170.
|
|
|
|
|
|
|
|
|
|
| |
functions.
Note that because this patch changes FmgrInfo, any external C functions
you might be testing with 8.4 will need to be recompiled.
Patch by Martin Pihlak, some editorialization by me (principally, removing
tracking of getrusage() numbers)
|
|
|
|
|
|
|
|
|
| |
file portability/instr_time.h, and add a couple more macros to eliminate
some abstraction leakage we formerly had. Also update psql to use this
header instead of its own copy of nearly the same code.
This commit in itself is just code cleanup and shouldn't change anything.
It lays some groundwork for the upcoming function-stats patch, though.
|
|
|
|
| |
heading at the top; broken into more sections now.
|
| |
|
|
|
|
|
|
|
|
|
| |
modes, replacing it with a call to a function that derives it from the
sync_method variable, now that it has distinct values for these two cases.
This means that assign_xlog_sync_method() no longer changes any settings,
thus fixing the bug introduced in the change to use a guc enum for
wal_sync_method.
|
|
|
|
|
|
|
|
|
| |
asked for anything other than RUSAGE_SELF, since it's not supported.
This is never called anywhere in the code today, but might be in
the future.
Not backpatching, since it's not called anywhere today.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
HINT fields to a user-thrown error message, and to specify the SQLSTATE
error code to use. The syntax has also been tweaked so that the
Oracle-compatible case "RAISE exception_name" works (though you won't get a
very nice error message if you just write that much). Lastly, support
the Oracle-compatible syntax "RAISE" with no parameters to re-throw
the current error from within an EXCEPTION block.
In passing, allow the syntax SQLSTATE 'nnnnn' within EXCEPTION lists,
so that there is a way to trap errors with custom SQLSTATE codes.
Pavel Stehule and Tom Lane
|
|
|
|
|
|
|
| |
crashes on certain platforms. In particular, the MSVC runtime is known
to do this.
Fixes bug #4162, reported and diagnosed by Javier Pimas
|
|
|
|
|
|
| |
consistent. OffsetNumberNext() has some casting that makes it useful.
Fujii Masao
|
|
|
|
|
|
| |
tables.
Brendan Jurd, with some help from me.
|
|
|
|
| |
before it was actually set.
|
|
|
|
|
|
|
|
| |
Provides for better code readability, but mainly this is infrastructure changes
to allow further changes such as arbitrary footers on printed tables. Also,
the translation status of each element in the table is more easily customized.
Brendan Jurd, with some editorialization by me.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two ways to track a snapshot: there's the "registered" list, which
is used for arbitrary long-lived snapshots; and there's the "active stack",
which is used for the snapshot that is considered "active" at any time.
This also allows users of snapshots to stop worrying about snapshot memory
allocation and freeing, and about using PG_TRY blocks around ActiveSnapshot
assignment. This is all done automatically now.
As a consequence, this allows us to reset MyProc->xmin when there are no
more snapshots registered in the current backend, reducing the impact that
long-running transactions have on VACUUM.
|
|
|
|
| |
O_DSYNC (specifically this broke all the Windows buildfarm members)
|
|
|
|
| |
Do not close files that weren't opened.
|
|
|
|
|
| |
Remove #include bufmgr.h from (most?) source files which already include
bufpage.h.
|
|
|
|
| |
not which one we had before (that worked, and thus is completley irrelevant)
|
| |
|