| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
| |
can create or modify rules for the table. Do setRuleCheckAsUser() while
loading rules into the relcache, rather than when defining a rule. This
ensures that permission checks for tables referenced in a rule are done with
respect to the current owner of the rule's table, whereas formerly ALTER TABLE
OWNER would fail to update the permission checking for associated rules.
Removal of separate RULE privilege is needed to prevent various scenarios
in which a grantee of RULE privilege could effectively have any privilege
of the table owner. For backwards compatibility, GRANT/REVOKE RULE is still
accepted, but it doesn't do anything. Per discussion here:
http://archives.postgresql.org/pgsql-hackers/2006-04/msg01138.php
|
|
|
|
| |
fix suggestion from Peter.
|
|
|
|
|
| |
'GIN FailedAssertions on Itanium2 with Intel compiler' in pgsql-hackers,
http://archives.postgresql.org/pgsql-hackers/2006-08/msg01914.php
|
| |
|
|
|
|
| |
Added some interval checks to regression suite.
|
|
|
|
|
| |
Fixed ecpglib trying to read one character after end-of-string.
Fixed port number setting in regression suite.
|
|
|
|
| |
Bruce, Michael Glaesemann
|
|
|
|
|
| |
position_in_unique_constraint (column newly added per SQL2003).
Greg Mullane
|
|
|
|
|
|
| |
second scan of table).
Gregory Stark
|
|
|
|
| |
Magnus Hagander
|
|
|
|
|
|
|
| |
the target relation(s). There might be some cases where we could discard
the pending event instead, but for the moment a conservative approach
seems sufficient. Per report from Markus Schiltknecht and subsequent
discussion.
|
|
|
|
|
|
|
| |
of 'S', and the views were not checking for table visibility with
regards to temporary tables and sequences.
Greg Sabino Mullane
|
|
|
|
| |
some platforms.
|
|
|
|
|
|
|
| |
working in a multibyte encoding. This fixes the problems exhibited in
bug #1931 and other reports of ILIKE misbehavior in UTF8 encoding.
It's a pretty grotty solution though --- should rethink how to do it
after we install better locale support, someday.
|
|
|
|
| |
Author: Victor Wagner <vitus@cryptocom.ru>
|
| |
|
|
|
|
|
|
|
| |
cascaded first to days and only what is leftover into seconds. This
seems to satisfy the principle of least surprise given the general
conversion to three-part interval values --- it was an oversight that
these cases weren't dealt with in 8.1. Michael Glaesemann
|
|
|
|
|
|
| |
of the syntax as this fundamentally dead-end approach can, in particular
combinations of single and multi column assignments. Improve rather
inadequate documentation and provide some regression tests.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
PGPROC array into snapshots, and use this information to avoid visits
to pg_subtrans in HeapTupleSatisfiesSnapshot. This appears to solve
the pg_subtrans-related context swap storm problem that's been reported
by several people for 8.1. While at it, modify GetSnapshotData to not
take an exclusive lock on ProcArrayLock, as closer analysis shows that
shared lock is always sufficient.
Itagaki Takahiro and Tom Lane
|
|
|
|
| |
Added another regression test and fixed tcp test.
|
|
|
|
|
|
|
| |
multiplication/division queries like select '41 mon 10:00:00'::interval
/ 10 as "pos".
Report from Michael Glaesemann
|
|
|
|
| |
fetch/move in scan.l.
|
|
|
|
| |
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.
|