| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
'simple' references another view that is not simple. Must recheck
conditions after performing recursive pullup. Per example from
Laurent Perez, 9-Jan-04.
|
| |
|
| |
|
|
|
|
|
| |
number-of-buckets that exceeds the size we actually plan to allow
the hash table to grow to. Per trouble report from Sean Shanny.
|
|
|
|
|
| |
ill-considered conditional logic in getpeereid patch of 3-Dec-2002).
Per bug #1021.
|
|
|
|
| |
untrusted languages (in case they sneak in).
|
|
|
|
| |
unsigned integers). Per report from Jim Crate.
|
|
|
|
|
| |
partially-evaluated SRFs. Per report found here:
http://archives.postgresql.org/pgsql-general/2003-12/msg00851.php
|
|
|
|
| |
Per Neil Conway.
|
|
|
|
|
| |
evaluating a set-valued function. This fixes some additional problems
with rescanning partially-evaluated SRFs.
|
|
|
|
|
|
| |
shut down cleanly if the plan node is ReScanned before the SRFs are run
to completion. This fixes the problem for SQL-language functions, but
still need work on functions using the SRF_XXX() macros.
|
|
|
|
|
| |
not discriminate against system columns, since we support constraints on
system columns, and in fact constraints on OID are moderately useful.
|
| |
|
|
|
|
|
|
| |
does not affect UNKNOWN-type literals or Params. This fixes the recent
complaint about count('x') being broken, and improves consistency in
a few other respects too.
|
|
|
|
|
|
|
| |
a join in its subselect. In this situation we *must* build a bushy
plan because there are no valid left-sided or right-sided join trees.
Accordingly, hoary sanity check needs an update. Per report from
Alessandro Depase.
|
| |
|
|
|
|
|
|
|
| |
planning to modify them itself. Otherwise we end up with shared RTE
substructure, which breaks inheritance_planner because the rte->inh
flag needs to be independent in each copied subquery. Per bug report
from Chris Piker.
|
|
|
|
|
| |
attr_needed/attr_widths optimization failed to allow for Vars with attno
zero in this case. Per report from Tatsuo Ishii.
|
|
|
|
|
| |
prevents view from showing constraints on domains. This addresses the
other half of Claus Colloseus' bug report.
|
|
|
|
| |
for bit(x), the typmod stores x+4, like for the character types.)
|
|
|
|
|
| |
functionality. Per bug report by Alvar Freude:
http://archives.postgresql.org/pgsql-bugs/2003-12/msg00022.php
|
| |
|
|
|
|
|
|
| |
and hash bucket-size estimation. Issue has been there awhile but is more
critical in 7.4 because it affects varchar columns. Per report from
Greg Stark.
|
|
|
|
| |
per gripe from Joe Sunday.
|
|
|
|
|
| |
since there is no need to worry about damaged pages when we are going to
overwrite them anyway from the WAL. Per recent discussion.
|
|
|
|
|
|
| |
octal escape all octets outside the range 0x20 to 0x7e. This fixes
the problem pointed out by Sergey Yatskevich here:
http://archives.postgresql.org/pgsql-bugs/2003-11/msg00140.php
|
|
|
|
|
|
| |
Ward's report that it can still happen in RC2 forces me to realize that
this is not a can't-happen condition after all, and that the compaction
code had better cope rather than panicking.
|
|
|
|
|
|
|
| |
Vars created to fill subplan args lists. This is an ancient error, going
back at least to 7.0, but is more easily triggered in 7.4 than before
because we no longer compare varlevelsup when deciding whether a Param
slot can be re-used. Fixes bug reported by Klint Gore.
|
|
|
|
|
|
|
|
|
|
| |
per report from Andrew Holm-Hansen. The difficulty arises from the fact
that the planner allowed a Hash node's hashkeys to share substructure
with the parent HashJoin node's hashclauses, plus some rather bizarre
choices about who initializes what during executor startup. A cleaner
but more invasive solution is to not store hashkeys separately in the
plan tree at all, but let the HashJoin node deconstruct hashclauses
during executor startup. I plan to fix it that way in HEAD.
|
|
|
|
|
|
| |
tree for CYCLE option; don't assume zeros are invalid values for sequence
fields other than increment_by; don't reset cache_value when not told to;
simplify code for testing whether to apply defaults.
|
| |
|
|
|
|
|
|
| |
which had been unintentionally broken by recent changes to tighten up the
DateStyle rules for all-numeric date input. Add documentation and
regression tests for this, too.
|
| |
|
|
|
|
|
| |
to try additional addresses returned from getaddrinfo() if the first one
fails at the bind() or connect() steps. Per yesterday's discussion.
|
| |
|
| |
|
|
|
|
| |
in HEAD.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
they do not prevent the postmaster from deleting the shmem segment during
a post-backend-crash restart cycle. Per recent discussion.
|
|
|
|
|
| |
else it cannot be used to handle failures detected during WAL replay.
Fortunately this flag isn't actually enforced yet, but get it right.
|
|
|
|
|
|
|
|
|
|
|
| |
regression=# select 1 from tenk1 ta cross join tenk1 tb for update;
ERROR: no relation entry for relid 3
7.3 said "SELECT FOR UPDATE cannot be applied to a join", which was better
but still wrong, considering that 7.2 took the query just fine. Fix by
making transformForUpdate() ignore JOIN and other special RTE types,
rather than trying to mark them FOR UPDATE. The actual error message now
only appears if you explicitly name the join in FOR UPDATE.
|
|
|
|
| |
Neil Conway.
|
|
|
|
|
|
|
|
|
| |
process the command as though it were issued by the object owner.
This prevents creating weird scenarios in which the same privileges
may appear to flow from different sources, and ensures that a superuser
can in fact revoke all privileges if he wants to. In particular this
means that the regression tests work when run by a superuser other than
the original bootstrap userid. Per report from Larry Rosenman.
|
|
|
|
|
|
|
|
| |
rule split the query into one INSERT and one UPDATE where the UPDATE
then hit's the just created row without modifying the key fields again.
In this special case, the new key slipped in totally unchecked.
Jan
|
|
|
|
|
|
| |
ACL array, and force languages to be treated as owned by the bootstrap
user ID. (pg_language should have a lanowner column, but until it does
this will have to do as a workaround.)
|
|
|
|
| |
Per example from Ian Barwick, 28-Oct-03.
|
|
|
|
|
| |
FSM data has to be both moved down and compressed. Per report from
Dror Matalon.
|
| |
|