| Age | Commit message (Collapse) | Author |
|---|
|
Report from Josh Tolley.
|
|
|
|
|
|
--- was part of autovacuum default 'on' patch that was reverted, but we
want this part.
Peter Eisentraut
|
|
|
|
possible autovacuum use.
|
|
|
|
multiple columns
Susanne Ebrecht
|
|
Dhanaraj M
|
|
Suppress some NOTICE messages from REINDEX command.
Euler Taveira de Oliveira
|
|
overhead for every connection, per Tom.
|
|
RETURNING play nice with views/rules. To wit, have the rule rewriter
rewrite any RETURNING clause found in a rule to produce what the rule's
triggering query asked for in its RETURNING clause, in particular drop
the RETURNING clause if no RETURNING in the triggering query. This
leaves the responsibility for knowing how to produce the view's output
columns on the rule author, without requiring any fundamental changes
in rule semantics such as adding new rule event types would do. The
initial implementation constrains things to ensure that there is
exactly one, unconditionally invoked RETURNING clause among the rules
for an event --- later we might be able to relax that, but for a post
feature freeze fix it seems better to minimize how much invention we do.
Per gripe from Jaime Casanova.
|
|
"server_version" but uses the handy PG_VERSION_NUM which allows apps to
do things like if ($version >= 80200) without having to parse apart the
value of server_version themselves.
Greg Sabino Mullane greg@turnstep.com
|
|
Sven Suursoho
|
|
Euler Taveira de Oliveira
|
|
didn't create a dependency from the new conversion to its schema. Back-patch
to all supported releases.
|
|
|
|
|
|
COPY SELECT work done by Zoltan Boszormenyi
|
|
Bernd Helmle
|
|
|
|
and other special flags on Windows. May fix intermittent 'Permission
denied' errors. Magnus Hagander
|
|
the pager before reporting the error.
|
|
queries via a cursor, fetching a limited number of rows at a time and
therefore not risking exhausting memory. A disadvantage of the scheme
is that 'aligned' output mode will align each group of rows independently
leading to odd-looking output, but all the other output formats work
reasonably well. Chris Mair, with some additional hacking by moi.
|
|
Fix printing of NULL bind parameters, use "NULL".
|
|
|
|
existing for backend GUC variables, and use this to eliminate repeated
fetching/parsing of psql variables in psql's inner loops. In a trivial
test with lots of 'select 1;' commands, psql's CPU time went down almost
10%, although of course the effect on total elapsed time was much less.
Per discussion about how to ensure the upcoming FETCH_COUNT patch doesn't
cost any performance when not being used.
|
|
|
|
|
|
Changed file paths in expected files too.
|
|
Streamlined connection name parsing.
Added Joachim's patch to shorten paths before diffing.
|
|
|
|
|
|
optionally bind. I re-added the "statement:" label so people will
understand why the line is being printed (it is log_*statement
behavior).
Use single quotes for bind values, instead of double quotes, and double
literal single quotes in bind values (and document that). I also made
use of the DETAIL line to have much cleaner output.
|
|
pgstat_bestart() has been called; else any lock-block occurring
during InitPostgres() is disastrous. I believe this explains
recent wasp regression failure; at least it explains the crash I
got while trying to duplicate the problem. I also made
pgstat_report_activity() safe against the same scenario, just
in case. The report_waiting hazard was created by my patch of
19-Aug to include waiting status in pg_stat_activity.
|
|
builds all the files needed for its regression tests, but the tests
themselves fail because of diffs in the #line directives output by
ecpg itself. Not sure what to do about that.
|
|
trivial if it contains either Vars referencing the corresponding subplan
columns, or Consts equaling the corresponding subplan columns. This
lets the planner eliminate the SubqueryScan in some cases generated by
generate_setop_tlist().
|
|
Threshold and scale factor are cut in half for more aggressive behavior.
|
|
Fix all the standard PLs to be able to return tuples from FOO_RETURNING
statements as well as utility statements that return tuples. Also,
fix oversight that SPI_processed wasn't set for a utility statement
returning tuples. Per recent discussion.
|
|
HeapTupleSatisfiesItself without doing LockBuffer first. This code
is a bit fragile, but AFAICS it's not actually broken.
|
|
locks that would conflict with a specified lock request, without
actually trying to get that lock. Use this instead of the former ad hoc
method of doing the first wait step in CREATE INDEX CONCURRENTLY.
Fixes problem with undetected deadlock and in many cases will allow the
index creation to proceed sooner than it otherwise could've. Per
discussion with Greg Stark.
|
|
Needed because lock.c is now going to use the same type of list.
|
|
- Fixed a memory leak/segfault in unsuccessful connection.
- Some changes to test files.
|
|
Per discussion with Martin Atukunda.
|
|
|
|
blocking concurrent writes to the table. Greg Stark, with a little help
from Tom Lane.
|
|
|
|
|
|
|
|
<RoccoA@Routescape.com>
|
