| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
<
> * Implement SQL:2003 window functions
|
| |
|
|
|
|
| |
order is changed.
|
|
|
|
|
| |
blocking concurrent writes to the table. Greg Stark, with a little help
from Tom Lane.
|
|
|
|
| |
Kaltenbrunner <stefan@kaltenbrunner.cc> and Phil Frost <indigo@bitglue.com>
|
|
|
|
| |
> * Allow inlining of set-returning functions
|
| |
|
| |
|
| |
|
|
|
|
| |
<RoccoA@Routescape.com>
|
|
|
|
|
| |
specific Windows error code (GetLastError). This is a hopefully temporary
hack to try to diagnose rare failures. Magnus Hagander
|
|
|
|
| |
John Gray
|
|
|
|
|
|
|
|
| |
on the same index page; we can avoid data copying as well as buffer refcount
manipulations in this common case. Makes for a small but noticeable
improvement in mergejoin speed.
Heikki Linnakangas
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
< * All backends running as threads in a single process (not want)
> * All backends running as threads in a single process (not wanted)
< * Optimizer hints (not want)
> * Optimizer hints (not wanted)
>
> * Allow AS in "SELECT col AS label" to be optional (not wanted)
>
> Because we support postfix operators, it isn't possible to make AS
> optional and continue to use bison.
> http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Use initializer string length as size for character strings.
Added ecpg_config.h file that is created via configure.
|
|
|
|
|
|
|
|
| |
< o Allow COPY to output from SELECT
> o Allow COPY (SELECT ...) TO 'filename'
< COPY should also be able to output views.
> COPY should also be able to output views using COPY (SELECT
> * FROM view) TO 'filename' internally.
|
|
|
|
| |
Fixed some regression test problems.
|
|
|
|
| |
"failure".
|
|
|
|
|
|
| |
>
> These would be for application use, not for use by pg_dump.
>
|
|
|
|
| |
suggesting review of client_encoding.
|
| |
|
|
|
|
| |
interchanged.
|
| |
|
|
|
|
|
| |
entirely on older Windows platforms without the needed library function.
Magnus Hagander
|
|
|
|
|
| |
the subject tuple is already deleted: we need not open the pk_rel
until after we check that.
|
| |
|
|
|
|
|
|
|
|
|
| |
of the transaction ID counter. Nothing is done with the epoch except to
store it in checkpoint records, but this provides a foundation with which
add-on code can pretend that XIDs never wrap around. This is a severely
trimmed and rewritten version of the xxid patch submitted by Marko Kreen.
Per discussion, the epoch counter seems the only part of xxid that really
needs to be in the core server.
|
|
|
|
|
| |
< o Add a function to support Parse/DescribeStatement capability
> o -Add a function to support Parse/DescribeStatement capability
|
|
|
|
|
|
|
|
|
|
| |
< * %Disallow changing DEFAULT expression of a SERIAL column?
<
< This should be done only if the existing SERIAL problems cannot be
< fixed.
<
< * %Disallow ALTER SEQUENCE changes for SERIAL sequences because pg_dump
< does not dump the changes
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
by abandoning the idea that it should say SERIAL in the dump. Instead,
dump serial sequences and column defaults just like regular ones.
Add a new backend command ALTER SEQUENCE OWNED BY to let pg_dump recreate
the sequence-to-column dependency that was formerly created "behind the
scenes" by SERIAL. This restores SERIAL to being truly "just a macro"
consisting of component operations that can be stated explicitly in SQL.
Furthermore, the new command allows sequence ownership to be reassigned,
so that old mistakes can be cleaned up.
Also, downgrade the OWNED-BY dependency from INTERNAL to AUTO, since there
is no longer any very compelling argument why the sequence couldn't be
dropped while keeping the column. (This forces initdb, to be sure the
right kinds of dependencies are in there.)
Along the way, add checks to prevent ALTER OWNER or SET SCHEMA on an
owned sequence; you can now only do this indirectly by changing the
owning table's owner or schema. This is an oversight in previous
releases, but probably not worth back-patching.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
each object to be deleted, instead of the previous hack that just skipped
INTERNAL dependencies, which didn't really work. Per report from Tom Lane.
To do this, introduce a new performMultipleDeletions entry point in
dependency.c to delete multiple objects at once. The dependency code then has
the responsability of tracking INTERNAL and AUTO dependencies as needed.
Along the way, change ObjectAddresses so that we can allocate an ObjectAddress
list from outside dependency.c and not have to export the internal
representation.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
functions in its targetlist, to avoid introducing multiple evaluations
of volatile functions that textually appear only once. This is a
slightly tighter version of Jaime Casanova's recent patch.
|