OSDN Git Service
Tom Lane [Wed, 4 Nov 2009 23:15:08 +0000 (23:15 +0000)]
Make expression locations for LIKE and SIMILAR TO constructs uniformly point
at the first keyword of the expression, rather than drawing a rather
artificial distinction between the ESCAPE subclause and the rest.
Per gripe from Gokulakannan Somasundaram and subsequent discusssion.
Tom Lane [Wed, 4 Nov 2009 22:26:08 +0000 (22:26 +0000)]
Add support for invoking parser callback hooks via SPI and in cached plans.
As proof of concept, modify plpgsql to use the hooks. plpgsql is still
inserting $n symbols textually, but the "back end" of the parsing process now
goes through the ParamRef hook instead of using a fixed parameter-type array,
and then execution only fetches actually-referenced parameters, using a hook
added to ParamListInfo.
Although there's a lot left to be done in plpgsql, this already cures the
"if (TG_OP = 'INSERT' and NEW.foo ...)" problem, as illustrated by the
changed regression test.
Heikki Linnakangas [Wed, 4 Nov 2009 12:51:30 +0000 (12:51 +0000)]
Disable triggering failover with a signal in pg_standby on Windows, because
Windows doesn't do signal processing like other platforms do. It never
really worked, but recent changes to the signal handling made it crash.
This fixes bug #4961. Patch by Fujii Masao.
Heikki Linnakangas [Wed, 4 Nov 2009 12:24:23 +0000 (12:24 +0000)]
Allow rewriting ALTER TABLE to skip WAL logging.
Itagaki Takahiro, with small changes by me and Simon.
Peter Eisentraut [Tue, 3 Nov 2009 21:28:10 +0000 (21:28 +0000)]
Build bzip2 tarball in dist target as well
Peter Eisentraut [Tue, 3 Nov 2009 14:52:10 +0000 (14:52 +0000)]
Fix regression tests for psql \d view patch
Peter Eisentraut [Tue, 3 Nov 2009 11:05:03 +0000 (11:05 +0000)]
Improve PL/Python elog output
When the elog functions (plpy.info etc.) get a single argument, just print
that argument instead of printing the single-member tuple like ('foo',).
Peter Eisentraut [Tue, 3 Nov 2009 10:34:47 +0000 (10:34 +0000)]
In psql, show view definition only with \d+, not with \d
The rationale is that view definitions tend to be long and obscure the
main information about the view.
Peter Eisentraut [Tue, 3 Nov 2009 09:35:18 +0000 (09:35 +0000)]
Fix obscure segfault condition in PL/Python
In PLy_output(), when the elog() call in the TRY branch throws an exception
(this can happen when a statement timeout kicks in, for example), the
PyErr_SetString() call in the CATCH branch can cause a segfault, because the
Py_XDECREF(so) call before it releases memory that is still used by the sv
variable that PyErr_SetString() uses as argument, because sv points into
memory owned by so.
Backpatched back to 8.0, where this code was introduced.
I also threw in a couple of volatile declarations for variables that are used
before and after the TRY. I don't think they caused the crash that I
observed, but they could become issues.
Tom Lane [Sun, 1 Nov 2009 22:30:54 +0000 (22:30 +0000)]
Dept of second thoughts: after studying index_getnext() a bit more I realize
that it can scribble on scan->xs_ctup.t_self while following HOT chains,
so we can't rely on that to stay valid between hashgettuple() calls.
Introduce a private variable in HashScanOpaque, instead.
Tom Lane [Sun, 1 Nov 2009 21:25:25 +0000 (21:25 +0000)]
Fix two serious bugs introduced into hash indexes by the 8.4 patch that made
hash indexes keep entries sorted by hash value. First, the original plans for
concurrency assumed that insertions would happen only at the end of a page,
which is no longer true; this could cause scans to transiently fail to find
index entries in the presence of concurrent insertions. We can compensate
by teaching scans to re-find their position after re-acquiring read locks.
Second, neither the bucket split nor the bucket compaction logic had been
fixed to preserve hashvalue ordering, so application of either of those
processes could lead to permanent corruption of an index, in the sense
that searches might fail to find entries that are present.
This patch fixes the split and compaction logic to preserve hashvalue
ordering, but it cannot do anything about pre-existing corruption. We will
need to recommend reindexing all hash indexes in the 8.4.2 release notes.
To buy back the performance loss hereby induced in split and compaction,
fix them to use PageIndexMultiDelete instead of retail PageIndexDelete
operations. We might later want to do something with qsort'ing the
page contents rather than doing a binary search for each insertion,
but that seemed more invasive than I cared to risk in a back-patch.
Per bug #5157 from Jeff Janes and subsequent investigation.
Tom Lane [Sat, 31 Oct 2009 18:11:59 +0000 (18:11 +0000)]
Ensure the previous Perl interpreter selection is restored upon exit from
plperl_call_handler, in both the normal and error-exit paths. Per report
from Alexey Klyukin.
Tom Lane [Sat, 31 Oct 2009 01:41:31 +0000 (01:41 +0000)]
Implement parser hooks for processing ColumnRef and ParamRef nodes, as per my
recent proposal. As proof of concept, remove knowledge of Params from the
core parser, arranging for them to be handled entirely by parser hook
functions. It turns out we need an additional hook for that --- I had
forgotten about the code that handles inferring a parameter's type from
context.
This is a preliminary step towards letting plpgsql handle its variables
through parser hooks. Additional work remains to be done to expose the
facility through SPI, but I think this is all the changes needed in the core
parser.
Tom Lane [Fri, 30 Oct 2009 20:58:45 +0000 (20:58 +0000)]
Make the overflow guards in ExecChooseHashTableSize be more protective.
The original coding ensured nbuckets and nbatch didn't exceed INT_MAX,
which while not insane on its own terms did nothing to protect subsequent
code like "palloc(nbatch * sizeof(BufFile *))". Since enormous join size
estimates might well be planner error rather than reality, it seems best
to constrain the initial sizes to be not more than work_mem/sizeof(pointer),
thus ensuring the allocated arrays don't exceed work_mem. We will allow
nbatch to get bigger than that during subsequent ExecHashIncreaseNumBatches
calls, but we should still guard against integer overflow in those palloc
requests. Per bug #5145 from Bernt Marius Johnsen.
Although the given test case only seems to fail back to 8.2, previous
releases have variants of this issue, so patch all supported branches.
Peter Eisentraut [Thu, 29 Oct 2009 21:57:17 +0000 (21:57 +0000)]
Remove some leftovers of split tarball support
Tom Lane [Wed, 28 Oct 2009 18:51:56 +0000 (18:51 +0000)]
Un-break EXPLAIN for Append plans. I messed this up a few days ago while
adding the ModifyTable node type --- I had been thinking ModifyTable should
replace Append as a special case in push_plan(), but actually both of them
have to be special-cased.
Tom Lane [Wed, 28 Oct 2009 18:09:44 +0000 (18:09 +0000)]
Fix \df to re-allow regexp special characters in the function name pattern.
This has always worked, up until somebody's thinko here:
http://archives.postgresql.org/pgsql-committers/2009-04/msg00233.php
Per bug #5143 from Piotr Wolinski.
Tom Lane [Wed, 28 Oct 2009 17:36:50 +0000 (17:36 +0000)]
Fix AcquireRewriteLocks to be sure that it acquires the right lock strength
when FOR UPDATE is propagated down into a sub-select expanded from a view.
Similar bug to parser's isLockedRel issue that I fixed yesterday; likewise
seems not quite worth the effort to back-patch.
Tom Lane [Wed, 28 Oct 2009 14:55:47 +0000 (14:55 +0000)]
When FOR UPDATE/SHARE is used with LIMIT, put the LockRows plan node
underneath the Limit node, not atop it. This fixes the old problem that such
a query might unexpectedly return fewer rows than the LIMIT says, due to
LockRows discarding updated rows.
There is a related problem that LockRows might destroy the sort ordering
produced by earlier steps; but fixing that by pushing LockRows below Sort
would create serious performance problems that are unjustified in many
real-world applications, as well as potential deadlock problems from locking
many more rows than expected. Instead, keep the present semantics of applying
FOR UPDATE after ORDER BY within a single query level; but allow the user to
specify the other way by writing FOR UPDATE in a sub-select. To make that
work, track whether FOR UPDATE appeared explicitly in sub-selects or got
pushed down from the parent, and don't flatten a sub-select that contained an
explicit FOR UPDATE.
Tom Lane [Tue, 27 Oct 2009 20:14:27 +0000 (20:14 +0000)]
Fix AfterTriggerSaveEvent to use a test and elog, not just Assert, to check
that it's called within an AfterTriggerBeginQuery/AfterTriggerEndQuery pair.
The RI cascade triggers suppress that overhead on the assumption that they
are always run non-deferred, so it's possible to violate the condition if
someone mistakenly changes pg_trigger to mark such a trigger deferred.
We don't really care about supporting that, but throwing an error instead
of crashing seems desirable. Per report from Marcelo Costa.
Tom Lane [Tue, 27 Oct 2009 17:11:18 +0000 (17:11 +0000)]
Make FOR UPDATE/SHARE in the primary query not propagate into WITH queries;
for example in
WITH w AS (SELECT * FROM foo) SELECT * FROM w, bar ... FOR UPDATE
the FOR UPDATE will now affect bar but not foo. This is more useful and
consistent than the original 8.4 behavior, which tried to propagate FOR UPDATE
into the WITH query but always failed due to assorted implementation
restrictions. Even though we are in process of removing those restrictions,
it seems correct on philosophical grounds to not let the outer query's
FOR UPDATE affect the WITH query.
In passing, fix isLockedRel which frequently got things wrong in
nested-subquery cases: "FOR UPDATE OF foo" applies to an alias foo in the
current query level, not subqueries. This has been broken for a long time,
but it doesn't seem worth back-patching further than 8.4 because the actual
consequences are minimal. At worst the parser would sometimes get
RowShareLock on a relation when it should be AccessShareLock or vice versa.
That would only make a difference if someone were using ExclusiveLock
concurrently, which no standard operation does, and anyway FOR UPDATE
doesn't result in visible changes so it's not clear that the someone would
notice any problem. Between that and the fact that FOR UPDATE barely works
with subqueries at all in existing releases, I'm not excited about worrying
about it.
Alvaro Herrera [Tue, 27 Oct 2009 13:58:28 +0000 (13:58 +0000)]
Fix documentation on the toast.fillfactor reloption: it doesn't exist.
Per note from Zoltan Boszormenyi.
Peter Eisentraut [Mon, 26 Oct 2009 21:33:01 +0000 (21:33 +0000)]
Simplify a few makefile rules since install-sh can now install multiple
files in one run.
Peter Eisentraut [Mon, 26 Oct 2009 21:11:22 +0000 (21:11 +0000)]
Check errors in for loop
Heikki Linnakangas [Mon, 26 Oct 2009 16:13:11 +0000 (16:13 +0000)]
Fix range check in date_recv that tried to limit accepted values to only
those accepted by date_in(). I confused julian day numbers and number of
days since the postgres epoch 2000-01-01 in the original patch.
I just noticed that it's still easy to get such out-of-range values into
the database using to_date or +- operators, but this patch doesn't do
anything about those functions.
Per report from James Pye.
Tom Lane [Mon, 26 Oct 2009 02:26:45 +0000 (02:26 +0000)]
Re-implement EvalPlanQual processing to improve its performance and eliminate
a lot of strange behaviors that occurred in join cases. We now identify the
"current" row for every joined relation in UPDATE, DELETE, and SELECT FOR
UPDATE/SHARE queries. If an EvalPlanQual recheck is necessary, we jam the
appropriate row into each scan node in the rechecking plan, forcing it to emit
only that one row. The former behavior could rescan the whole of each joined
relation for each recheck, which was terrible for performance, and what's much
worse could result in duplicated output tuples.
Also, the original implementation of EvalPlanQual could not re-use the recheck
execution tree --- it had to go through a full executor init and shutdown for
every row to be tested. To avoid this overhead, I've associated a special
runtime Param with each LockRows or ModifyTable plan node, and arranged to
make every scan node below such a node depend on that Param. Thus, by
signaling a change in that Param, the EPQ machinery can just rescan the
already-built test plan.
This patch also adds a prohibition on set-returning functions in the
targetlist of SELECT FOR UPDATE/SHARE. This is needed to avoid the
duplicate-output-tuple problem. It seems fairly reasonable since the
other restrictions on SELECT FOR UPDATE are meant to ensure that there
is a unique correspondence between source tuples and result tuples,
which an output SRF destroys as much as anything else does.
Peter Eisentraut [Fri, 23 Oct 2009 05:24:52 +0000 (05:24 +0000)]
When querying a table with child tables, do not check permissions on the
child tables. This was found to be useless and confusing in virtually all
cases, and also contrary to the SQL standard.
Tom Lane [Wed, 21 Oct 2009 20:38:58 +0000 (20:38 +0000)]
Remove regex_flavor GUC, so that regular expressions are always "advanced"
style by default. Per discussion, there seems to be hardly anything that
really relies on being able to change the regex flavor, so the ability to
select it via embedded options ought to be enough for any stragglers.
Also, if we didn't remove the GUC, we'd really be morally obligated to
mark the regex functions non-immutable, which'd possibly create performance
issues.
Tom Lane [Wed, 21 Oct 2009 20:22:38 +0000 (20:22 +0000)]
Remove add_missing_from GUC and associated parser support for "implicit RTEs".
Per recent discussion, add_missing_from has been deprecated for long enough to
consider removing, and it's getting in the way of planned parser refactoring.
The system now always behaves as though add_missing_from were OFF.
Peter Eisentraut [Wed, 21 Oct 2009 19:43:06 +0000 (19:43 +0000)]
Finalize 8.5alpha2 release notes, with updates from Josh Berkus
Peter Eisentraut [Tue, 20 Oct 2009 19:52:58 +0000 (19:52 +0000)]
Preliminary release notes for 8.5alpha2
Peter Eisentraut [Tue, 20 Oct 2009 18:23:27 +0000 (18:23 +0000)]
Translations update for 8.5alpha2
Peter Eisentraut [Tue, 20 Oct 2009 18:22:19 +0000 (18:22 +0000)]
Update translation updating procedure. This pertains to some changes I
made to automatically exclude translations below the 80% minimum.
Magnus Hagander [Sat, 17 Oct 2009 05:14:52 +0000 (05:14 +0000)]
Fix typo in previous release as reported by Itagaki Takahiro, but missed
by me.
Magnus Hagander [Sat, 17 Oct 2009 00:24:51 +0000 (00:24 +0000)]
Write to the Windows eventlog in UTF16, converting the message encoding
as necessary.
Itagaki Takahiro with some changes from me
Tom Lane [Fri, 16 Oct 2009 22:08:36 +0000 (22:08 +0000)]
Rewrite pam_passwd_conv_proc to be more robust: avoid assuming that the
pam_message array contains exactly one PAM_PROMPT_ECHO_OFF message.
Instead, deal with however many messages there are, and don't throw error
for PAM_ERROR_MSG and PAM_TEXT_INFO messages. This logic is borrowed from
openssh 5.2p1, which hopefully has seen more real-world PAM usage than we
have. Per bug #5121 from Ryan Douglas, which turned out to be caused by
the conv_proc being called with zero messages. Apparently that is normal
behavior given the combination of Linux pam_krb5 with MS Active Directory
as the domain controller.
Patch all the way back, since this code has been essentially untouched
since 7.4. (Surprising we've not heard complaints before.)
Heikki Linnakangas [Fri, 16 Oct 2009 10:38:25 +0000 (10:38 +0000)]
FREEZE and VERBOSE options were in wrong order in the VACUUM command that
vacuumdb produces. Per report by Thom Brown.
Tom Lane [Thu, 15 Oct 2009 23:39:13 +0000 (23:39 +0000)]
First committed version of plpython_unicode_0.out did not actually contain the
required \200 bytes. Let's see if this commit works, or if CVS is messing it up.
Michael Meskes [Thu, 15 Oct 2009 10:20:15 +0000 (10:20 +0000)]
Made ECPG more robust against applications freeing strings, based on
patch send in by Boszormenyi Zoltan <zb@cybertec.at>.
Alvaro Herrera [Wed, 14 Oct 2009 23:36:43 +0000 (23:36 +0000)]
Avoid using trivial usernames in foreign_data regression test.
Author: Martin Pihlak
Tom Lane [Wed, 14 Oct 2009 22:14:25 +0000 (22:14 +0000)]
Support SQL-compliant triggers on columns, ie fire only if certain columns
are named in the UPDATE's SET list.
Note: the schema of pg_trigger has not actually changed; we've just started
to use a column that was there all along. catversion bumped anyway so that
this commit is included in the history of potentially interesting changes
to system catalog contents.
Itagaki Takahiro
Heikki Linnakangas [Wed, 14 Oct 2009 22:09:46 +0000 (22:09 +0000)]
Rename the new MAX_AUTH_TOKEN_LENGTH #define to PG_MAX_AUTH_MAX_TOKEN_LENGTH,
to make it more obvious that it's a PostgreSQL internal limit, not something
that comes from system header files.
Peter Eisentraut [Wed, 14 Oct 2009 21:59:15 +0000 (21:59 +0000)]
In the configure check for the Python distutils module, use a less obscure
shell construct to hide away the stderr output. Python 3.1 actually core
dumps on the current invocation (http://bugs.python.org/issue7111), but the
new version also has the more general advantage of saving the error message
in config.log for analysis.
Peter Eisentraut [Wed, 14 Oct 2009 21:42:58 +0000 (21:42 +0000)]
Add alternative expected file for unicode test for client encoding not UTF8
Heikki Linnakangas [Wed, 14 Oct 2009 07:27:13 +0000 (07:27 +0000)]
Raise the maximum authentication token (Kerberos ticket) size in GSSAPI
and SSPI athentication methods. While the old 2000 byte limit was more than
enough for Unix Kerberos implementations, tickets issued by Windows Domain
Controllers can be much larger.
Ian Turner
Peter Eisentraut [Tue, 13 Oct 2009 22:46:13 +0000 (22:46 +0000)]
Replace unmatched " by " to avoid throwing off syntax highlighters.
Tom Lane [Tue, 13 Oct 2009 21:04:01 +0000 (21:04 +0000)]
Add "\pset linestyle ascii/unicode" option to psql, allowing our traditional
ASCII-art style of table output to be upgraded to use Unicode box drawing
characters if desired. By default, psql will use the Unicode characters
whenever client_encoding is UTF8.
The patch forces linestyle=ascii in pg_regress usage, ensuring we don't
break the regression tests in Unicode locales.
Roger Leigh
Tom Lane [Tue, 13 Oct 2009 14:33:14 +0000 (14:33 +0000)]
Fix ts_stat's failure on empty tsvector.
Also insert a couple of Asserts that check for stack overflow.
Bogus coding appears to be new in 8.4 --- older releases had a much
simpler algorithm here. Per bug #5111.
Alvaro Herrera [Tue, 13 Oct 2009 14:18:40 +0000 (14:18 +0000)]
Add new PGC_S_DATABASE_USER enum value to several places missed by my patch
last week.
Per note and patch from Jeff Davis.
Tom Lane [Tue, 13 Oct 2009 00:53:08 +0000 (00:53 +0000)]
Code review for LIKE INCLUDING patch --- clean up some cosmetic and not
so cosmetic stuff.
Tom Lane [Mon, 12 Oct 2009 23:41:45 +0000 (23:41 +0000)]
Use plurals (TABLES, FUNCTIONS, etc) in ALTER DEFAULT PRIVILEGES. We have
the keywords as a consequence of the GRANT ALL patch, so we might as well
use them and make the ALTER commands read more naturally.
Tom Lane [Mon, 12 Oct 2009 20:39:42 +0000 (20:39 +0000)]
Support GRANT/REVOKE ON ALL TABLES/SEQUENCES/FUNCTIONS IN SCHEMA.
Petr Jelinek
Andrew Dunstan [Mon, 12 Oct 2009 19:49:24 +0000 (19:49 +0000)]
CREATE LIKE INCLUDING COMMENTS and STORAGE, and INCLUDING ALL shortcut. Itagaki Takahiro.
Tom Lane [Mon, 12 Oct 2009 18:10:51 +0000 (18:10 +0000)]
Move the handling of SELECT FOR UPDATE locking and rechecking out of
execMain.c and into a new plan node type LockRows. Like the recent change
to put table updating into a ModifyTable plan node, this increases planning
flexibility by allowing the operations to occur below the top level of the
plan tree. It's necessary in any case to restore the previous behavior of
having FOR UPDATE locking occur before ModifyTable does.
This partially refactors EvalPlanQual to allow multiple rows-under-test
to be inserted into the EPQ machinery before starting an EPQ test query.
That isn't sufficient to fix EPQ's general bogosity in the face of plans
that return multiple rows per test row, though. Since this patch is
mostly about getting some plan node infrastructure in place and not about
fixing ten-year-old bugs, I will leave EPQ improvements for another day.
Another behavioral change that we could now think about is doing FOR UPDATE
before LIMIT, but that too seems like it should be treated as a followon
patch.
Tom Lane [Sat, 10 Oct 2009 03:50:15 +0000 (03:50 +0000)]
Improve similar_escape() in two different ways:
* Stop escaping ? and {. As of SQL:2008, SIMILAR TO is defined to have
POSIX-compatible interpretation of ? as well as {m,n} and related constructs,
so we should allow these things through to our regex engine.
* Escape ^ and $. It appears that our regex engine will treat ^^ at the
beginning of the string the same as ^, and similarly for $$ at the end of
the string, which meant that SIMILAR TO was effectively ignoring ^ at the
start of the pattern and $ at the end. Since these are not supposed to be
metacharacters, this is a bug.
The second part of this is arguably a back-patchable bug fix, but I'm
hesitant to do that because it might break applications that are expecting
something like "col SIMILAR TO '^foo$'" to work like a POSIX pattern.
Seems safer to only change it at a major version boundary.
Per discussion of an example from Doug Gorley.
Tom Lane [Sat, 10 Oct 2009 01:43:50 +0000 (01:43 +0000)]
Split the processing of INSERT/UPDATE/DELETE operations out of execMain.c.
They are now handled by a new plan node type called ModifyTable, which is
placed at the top of the plan tree. In itself this change doesn't do much,
except perhaps make the handling of RETURNING lists and inherited UPDATEs a
tad less klugy. But it is necessary preparation for the intended extension of
allowing RETURNING queries inside WITH.
Marko Tiikkaja
Peter Eisentraut [Fri, 9 Oct 2009 21:02:56 +0000 (21:02 +0000)]
Use pg_get_triggerdef in pg_dump
Add a variant of pg_get_triggerdef with a second argument "pretty" that
causes the output to be formatted in the way pg_dump used to do. Use this
variant in pg_dump with server versions >= 8.5.
This insulates pg_dump from most future trigger feature additions, such as
the upcoming column triggers patch.
Author: Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>
Tom Lane [Thu, 8 Oct 2009 22:34:57 +0000 (22:34 +0000)]
Remove very ancient tuple-counting infrastructure (IncrRetrieved() and
friends). This code has all been ifdef'd out for many years, and doesn't
seem to have any prospect of becoming any more useful in the future.
EXPLAIN ANALYZE is what people use in practice, and I think if we did want
process-wide counters we'd be more likely to put in dtrace events for that
than try to resurrect this code. Get rid of it so as to have one less detail
to worry about while refactoring execMain.c.
Alvaro Herrera [Thu, 8 Oct 2009 16:34:01 +0000 (16:34 +0000)]
Add the new psql command \drds to the psql docs, help and tab completion.
I also thank Bernd Helmle for the documentation help on the previous settings
patch, which I forgot on the commit message.
Heikki Linnakangas [Thu, 8 Oct 2009 04:46:21 +0000 (04:46 +0000)]
Fix off-by-one bug in bitncmp(): When comparing a number of bits divisible by
8, bitncmp() may dereference a pointer one byte out of bounds.
Chris Mikkelson (bug #5101)
Tom Lane [Thu, 8 Oct 2009 04:41:07 +0000 (04:41 +0000)]
Update plhandler.sgml to describe validators and inline handlers for
procedural languages.
Tom Lane [Thu, 8 Oct 2009 02:39:25 +0000 (02:39 +0000)]
Support use of function argument names to identify which actual arguments
match which function parameters. The syntax uses AS, for example
funcname(value AS arg1, anothervalue AS arg2)
Pavel Stehule
Alvaro Herrera [Wed, 7 Oct 2009 22:14:26 +0000 (22:14 +0000)]
Make it possibly to specify GUC params per user and per database.
Create a new catalog pg_db_role_setting where they are now stored, and better
encapsulate the code that deals with settings into its realm. The old
datconfig and rolconfig columns are removed.
psql has gained a \drds command to display the settings.
Backwards compatibility warning: while the backwards-compatible system views
still have the config columns, they no longer completely represent the
configuration for a user or database.
Catalog version bumped.
Alvaro Herrera [Wed, 7 Oct 2009 16:27:18 +0000 (16:27 +0000)]
Fix snapshot management, take two.
Partially revert the previous patch I installed and replace it with a more
general fix: any time a snapshot is pushed as Active, we need to ensure that it
will not be modified in the future. This means that if the same snapshot is
used as CurrentSnapshot, it needs to be copied separately. This affects
serializable transactions only, because CurrentSnapshot has already been copied
by RegisterSnapshot and so PushActiveSnapshot does not think it needs another
copy. However, CommandCounterIncrement would modify CurrentSnapshot, whereas
ActiveSnapshots must not have their command counters incremented.
I say "partially" because the regression test I added for the previous bug
has been kept.
(This restores 8.3 behavior, because before snapmgr.c existed, any snapshot set
as Active was copied.)
Per bug report from Stuart Bishop in
6bc73d4c0910042358k3d1adff3qa36f8df75198ecea@mail.gmail.com
Peter Eisentraut [Tue, 6 Oct 2009 20:00:44 +0000 (20:00 +0000)]
Clean up the clean rules of the documentation
Most things should be cleaned by "make clean", except the parts that are
shipped in the tarball. These rules had gotten a bit out of whack after
the various restructurings of the documentation build rules.
Tom Lane [Tue, 6 Oct 2009 00:55:26 +0000 (00:55 +0000)]
Change CREATE TABLE so that column default expressions coming from different
inheritance parent tables are compared using equal(), instead of doing
strcmp() on the nodeToString representation. The old implementation was
always a tad cheesy, and it finally fails completely as of 8.4, now that the
node tree might contain syntax location information. equal() knows it's
supposed to ignore those fields, but strcmp() hardly can. Per recent
report from Scott Ribe.
Alvaro Herrera [Tue, 6 Oct 2009 00:54:26 +0000 (00:54 +0000)]
Really unbreak maintainer-clean.
(Or rather, unbreak what the previous commit broke)
Alvaro Herrera [Mon, 5 Oct 2009 23:58:49 +0000 (23:58 +0000)]
Unbreak doc/src/sgml maintainer-clean rule on VPATH builds.
Tom Lane [Mon, 5 Oct 2009 19:24:49 +0000 (19:24 +0000)]
Create an ALTER DEFAULT PRIVILEGES command, which allows users to adjust
the privileges that will be applied to subsequently-created objects.
Such adjustments are always per owning role, and can be restricted to objects
created in particular schemas too. A notable benefit is that users can
override the traditional default privilege settings, eg, the PUBLIC EXECUTE
privilege traditionally granted by default for functions.
Petr Jelinek
Bruce Momjian [Sat, 3 Oct 2009 23:10:47 +0000 (23:10 +0000)]
Document the purpose of the GUC listen_addresses.
Tom Lane [Sat, 3 Oct 2009 20:04:39 +0000 (20:04 +0000)]
Fix assorted memory leaks in pg_hba.conf parsing. Over a sufficiently
large number of SIGHUP cycles, these would have run the postmaster out
of memory. Noted while testing memory-leak scenario in postgresql.conf
configuration-change-printing patch.
Tom Lane [Sat, 3 Oct 2009 18:04:57 +0000 (18:04 +0000)]
Fix a couple of issues in recent patch to print updates to postgresql.conf
settings: avoid calling superuser() in contexts where it's not defined,
don't leak the transient copies of GetConfigOption output, and avoid the
whole exercise in postmaster child processes.
I found that actually no current caller of GetConfigOption has any use for
its internal check of GUC_SUPERUSER_ONLY. But rather than just remove
that entirely, it seemed better to add a parameter indicating whether to
enforce the check.
Per report from Simon and subsequent testing.
Tom Lane [Fri, 2 Oct 2009 22:49:50 +0000 (22:49 +0000)]
Fix an oversight in an 8.3-era patch: pgstat_initstats should allow stats
to be collected for sequences.
Report and fix by Akira Kurosawa
Tom Lane [Fri, 2 Oct 2009 21:14:04 +0000 (21:14 +0000)]
Make sure that GIN fast-insert and regular code paths enforce the same
tuple size limit. Improve the error message for index-tuple-too-large
so that it includes the actual size, the limit, and the index name.
Sync with the btree occurrences of the same error.
Back-patch to 8.4 because it appears that the out-of-sync problem
is occurring in the field.
Teodor and Tom
Tom Lane [Fri, 2 Oct 2009 18:13:04 +0000 (18:13 +0000)]
Fix erroneous handling of shared dependencies (ie dependencies on roles)
in CREATE OR REPLACE FUNCTION. The original code would update pg_shdepend
as if a new function was being created, even if it wasn't, with two bad
consequences: pg_shdepend might record the wrong owner for the function,
and any dependencies for roles mentioned in the function's ACL would be lost.
The fix is very easy: just don't touch pg_shdepend at all when doing a
function replacement.
Also update the CREATE FUNCTION reference page, which never explained
exactly what changes and doesn't change in a function replacement.
In passing, fix the CREATE VIEW reference page similarly; there's no
code bug there, but the docs didn't say what happens.
Alvaro Herrera [Fri, 2 Oct 2009 17:57:30 +0000 (17:57 +0000)]
Ensure that a cursor has an immutable snapshot throughout its lifespan.
The old coding was using a regular snapshot, referenced elsewhere, that was
subject to having its command counter updated. Fix by creating a private copy
of the snapshot exclusively for the cursor.
Backpatch to 8.4, which is when the bug was introduced during the snapshot
management rewrite.
Michael Meskes [Thu, 1 Oct 2009 18:03:54 +0000 (18:03 +0000)]
Applied patch by Boszormenyi Zoltan <zb@cybertec.at> to fix memory leak in decimal handling.
Tom Lane [Thu, 1 Oct 2009 01:58:58 +0000 (01:58 +0000)]
Support "samehost" and "samenet" specifications in pg_hba.conf,
by enumerating the machine's IP interfaces to look for a match.
Stef Walter
Tom Lane [Wed, 30 Sep 2009 21:26:17 +0000 (21:26 +0000)]
Fix bogus Assert, per buildfarm results.
Tom Lane [Wed, 30 Sep 2009 19:50:22 +0000 (19:50 +0000)]
Assorted improvements in contrib/hstore.
Remove the 64K limit on the lengths of keys and values within an hstore.
(This changes the on-disk format, but the old format can still be read.)
Add support for btree/hash opclasses for hstore --- this is not so much
for actual indexing purposes as to allow use of GROUP BY, DISTINCT, etc.
Add various other new functions and operators.
Andrew Gierth
Peter Eisentraut [Tue, 29 Sep 2009 20:25:01 +0000 (20:25 +0000)]
Add tooltips to the header links, and make title a link to the home page
based on an idea by Richard Huxton
Tom Lane [Tue, 29 Sep 2009 20:05:29 +0000 (20:05 +0000)]
Allow MOVE FORWARD n, MOVE BACKWARD n, MOVE FORWARD ALL, MOVE BACKWARD ALL
in plpgsql. Clean up a couple of corner cases in the MOVE/FETCH syntax.
Pavel Stehule
Tom Lane [Tue, 29 Sep 2009 01:20:34 +0000 (01:20 +0000)]
Fix equivclass.c's not-quite-right strategy for handling X=X clauses.
The original coding correctly noted that these aren't just redundancies
(they're effectively X IS NOT NULL, assuming = is strict). However, they
got treated that way if X happened to be in a single-member EquivalenceClass
already, which could happen if there was an ORDER BY X clause, for instance.
The simplest and most reliable solution seems to be to not try to process
such clauses through the EquivalenceClass machinery; just throw them back
for traditional processing. The amount of work that'd be needed to be
smarter than that seems out of proportion to the benefit.
Per bug #5084 from Bernt Marius Johnsen, and analysis by Andrew Gierth.
Andrew Dunstan [Mon, 28 Sep 2009 17:31:12 +0000 (17:31 +0000)]
Convert a perl array to a postgres array when returned by Set Returning Functions as well as non SRFs. Backpatch to 8.1 where these facilities were introduced. with a little help from Abhijit Menon-Sen.
Michael Meskes [Mon, 28 Sep 2009 08:50:57 +0000 (08:50 +0000)]
Added some explanation about how the parser is generated, taken from an email by
Zoltan Boszormenyi <zb@cybertec.at>.
Tom Lane [Sun, 27 Sep 2009 21:10:53 +0000 (21:10 +0000)]
Remove no-longer-needed ExecCountSlots infrastructure.
Tom Lane [Sun, 27 Sep 2009 20:09:58 +0000 (20:09 +0000)]
Replace the array-style TupleTable data structure with a simple List of
TupleTableSlot nodes. This eliminates the need to count in advance
how many Slots will be needed, which seems more than worth the small
increase in the amount of palloc traffic during executor startup.
The ExecCountSlots infrastructure is now all dead code, but I'll remove it
in a separate commit for clarity.
Per a comment from Robert Haas.
Tom Lane [Sun, 27 Sep 2009 03:43:10 +0000 (03:43 +0000)]
Make libpq reject non-numeric and out-of-range port numbers with a suitable
error message, rather than blundering on and failing with something opaque.
Sam Mason
Tom Lane [Sun, 27 Sep 2009 03:27:24 +0000 (03:27 +0000)]
Sync psql's scanner with recent changes in backend scanner's flex rules.
Marko Kreen, Tom Lane
Tom Lane [Sun, 27 Sep 2009 02:14:04 +0000 (02:14 +0000)]
Ooops, fix to Genbki.pm for ROWTYPE_OID wasn't quite right. Also, make a few
spacing tweaks so it produces exactly the same output as genbki.sh.
Tom Lane [Sun, 27 Sep 2009 01:32:11 +0000 (01:32 +0000)]
Simplify the bootstrap (BKI) code by getting rid of a useless table of all
the strings seen during the bootstrap run. There might have been some
actual point to doing that, many years ago, but as far as I can see the only
value now is to conserve a bit of memory. Even if we cared about wasting
a megabyte or so during the initdb run, it'd be far more effective to
arrange to release memory at the end of each BKI command, instead of
intentionally hanging onto strings that might never be used again.
Not maintaining the table probably makes it faster too; but the main point
of this patch is to get rid of a couple hundred lines of unnecessary and
rather crufty code.
Tom Lane [Sat, 26 Sep 2009 23:22:48 +0000 (23:22 +0000)]
Hmm, seems a lot of the buildfarm is running versions of awk that
don't have gensub(). Use sub() instead, tedious though it be.
Tom Lane [Sat, 26 Sep 2009 23:08:22 +0000 (23:08 +0000)]
Revert my ill-considered change that made formrdesc not insert the correct
relation rowtype OID into the relcache entries it builds. This ensures
that catcache copies of the relation tupdescs will be fully correct.
While the deficiency doesn't seem to have any effect in the current
sources, we have been bitten by not-quite-right catcache tupdescs before,
so it seems like a good idea to maintain the rule that they should be right.
Tom Lane [Sat, 26 Sep 2009 22:42:03 +0000 (22:42 +0000)]
Extend the BKI infrastructure to allow system catalogs to be given
hand-assigned rowtype OIDs, even when they are not "bootstrapped" catalogs
that have handmade type rows in pg_type.h. Give pg_database such an OID.
Restore the availability of C macros for the rowtype OIDs of the bootstrapped
catalogs. (These macros are now in the individual catalogs' .h files,
though, not in pg_type.h.)
This commit doesn't do anything especially useful by itself, but it's
necessary infrastructure for reverting some ill-considered changes in
relcache.c.
Tom Lane [Sat, 26 Sep 2009 18:24:49 +0000 (18:24 +0000)]
Fix RelationCacheInitializePhase2 (Phase3, in HEAD) to cope with the
possibility of shared-inval messages causing a relcache flush while it tries
to fill in missing data in preloaded relcache entries. There are actually
two distinct failure modes here:
1. The flush could delete the next-to-be-processed cache entry, causing
the subsequent hash_seq_search calls to go off into the weeds. This is
the problem reported by Michael Brown, and I believe it also accounts
for bug #5074. The simplest fix is to restart the hashtable scan after
we've read any new data from the catalogs. It appears that pre-8.4
branches have not suffered from this failure, because by chance there were
no other catalogs sharing the same hash chains with the catalogs that
RelationCacheInitializePhase2 had work to do for. However that's obviously
pretty fragile, and it seems possible that derivative versions with
additional system catalogs might be vulnerable, so I'm back-patching this
part of the fix anyway.
2. The flush could delete the *current* cache entry, in which case the
pointer to the newly-loaded data would end up being stored into an
already-deleted Relation struct. As long as it was still deleted, the only
consequence would be some leaked space in CacheMemoryContext. But it seems
possible that the Relation struct could already have been recycled, in
which case this represents a hard-to-reproduce clobber of cached data
structures, with unforeseeable consequences. The fix here is to pin the
entry while we work on it.
In passing, also change RelationCacheInitializePhase2 to Assert that
formrdesc() set up the relation's cached TupleDesc (rd_att) with the
correct type OID and hasoids values. This is more appropriate than
silently updating the values, because the original tupdesc might already
have been copied into the catcache. However this part of the patch is
not in HEAD because it fails due to some questionable recent changes in
formrdesc :-(. That will be cleaned up in a subsequent patch.
Peter Eisentraut [Fri, 25 Sep 2009 21:13:06 +0000 (21:13 +0000)]
Prevent isolated second surrogate in U& syntax
Peter Eisentraut [Fri, 25 Sep 2009 20:51:37 +0000 (20:51 +0000)]
Remove backup states from Unicode escapes patch
Tom Lane [Wed, 23 Sep 2009 15:41:51 +0000 (15:41 +0000)]
Improve example for DO, per Petr Jelinek.
Peter Eisentraut [Tue, 22 Sep 2009 23:52:53 +0000 (23:52 +0000)]
Unicode escapes in E'...' strings
Author: Marko Kreen <markokr@gmail.com>
Tom Lane [Tue, 22 Sep 2009 23:43:43 +0000 (23:43 +0000)]
Implement the DO statement to support execution of PL code without having
to create a function for it.
Procedural languages now have an additional entry point, namely a function
to execute an inline code block. This seemed a better design than trying
to hide the transient-ness of the code from the PL. As of this patch, only
plpgsql has an inline handler, but probably people will soon write handlers
for the other standard PLs.
In passing, remove the long-dead LANCOMPILER option of CREATE LANGUAGE.
Petr Jelinek