- Oct 13, 2009
- Oct 12, 2009
-
-
Tom Lane authored
Petr Jelinek
-
Andrew Dunstan authored
-
- Oct 10, 2009
-
-
Tom Lane authored
* 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 authored
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
-
- Oct 09, 2009
-
-
Peter Eisentraut authored
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>
-
- Oct 08, 2009
-
-
Alvaro Herrera authored
I also thank Bernd Helmle for the documentation help on the previous settings patch, which I forgot on the commit message.
-
Tom Lane authored
procedural languages.
-
Tom Lane authored
match which function parameters. The syntax uses AS, for example funcname(value AS arg1, anothervalue AS arg2) Pavel Stehule
-
Alvaro Herrera authored
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.
-
- Oct 06, 2009
-
-
Peter Eisentraut authored
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.
-
Alvaro Herrera authored
(Or rather, unbreak what the previous commit broke)
-
Alvaro Herrera authored
-
- Oct 05, 2009
-
-
Tom Lane authored
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
-
- Oct 04, 2009
-
-
Bruce Momjian authored
-
- Oct 02, 2009
-
-
Tom Lane authored
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.
-
- Oct 01, 2009
-
-
Tom Lane authored
by enumerating the machine's IP interfaces to look for a match. Stef Walter
-
- Sep 30, 2009
-
-
Tom Lane authored
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
-
- Sep 29, 2009
-
-
Peter Eisentraut authored
based on an idea by Richard Huxton
-
Tom Lane authored
in plpgsql. Clean up a couple of corner cases in the MOVE/FETCH syntax. Pavel Stehule
-
- Sep 27, 2009
-
-
Tom Lane authored
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.
-
- Sep 23, 2009
-
-
Tom Lane authored
-
Peter Eisentraut authored
Author: Marko Kreen <markokr@gmail.com>
-
Tom Lane authored
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
-
- Sep 22, 2009
-
-
Peter Eisentraut authored
This is mainly to make the functionality consistent with the proposed \u escape syntax.
-
- Sep 21, 2009
-
-
Tom Lane authored
This is intentionally similar to the recently revised syntax for EXPLAIN options, ie, (name value, ...). The old syntax is still supported for backwards compatibility, but we intend that any options added in future will be provided only in the new syntax. Robert Haas, Emmanuel Cecchet
-
- Sep 19, 2009
-
-
Peter Eisentraut authored
-
- Sep 18, 2009
-
-
Tom Lane authored
-
Michael Meskes authored
function that returns the current transaction status.
-
Peter Eisentraut authored
Instead of requiring translators to translate the entire SQL command synopses, change create_help.pl to only require them to translate the placeholders, and paste those into the synopsis using a printf mechanism. Make some small updates to the markup to make it easier to parse. Note: This causes msgmerge of gettext 0.17 to segfault. You will need the patch from https://savannah.gnu.org/bugs/?27474 to make it work. msgmerge usually only runs on babel.postgresql.org, however.
-
- Sep 17, 2009
-
-
Bruce Momjian authored
Update docs to clearly explain NULL value matching behavior, per Andrew. Backpatch to 8.4.X.
-
Bruce Momjian authored
Clearify documentation of CVS's output of NULL values, per suggestion from Magnus. Backpatch to 8.4.X.
-
- Sep 14, 2009
-
-
Peter Eisentraut authored
-
- Sep 13, 2009
-
-
Peter Eisentraut authored
per Joshua Tolley
-
- Sep 12, 2009
-
-
Tom Lane authored
privileges by mentioning the possibility of granting membership in the owning role.
-
- Sep 11, 2009
-
-
Tom Lane authored
use that value when the backend is new enough to allow it. This responds to bug report from Keh-Cheng Chu pointing out that although 2 extra digits should be sufficient to dump and restore float8 exactly, it is possible to need 3 extra digits for float4 values.
-
Peter Eisentraut authored
per Bruno Guimarães Carneiro
-
- Sep 10, 2009
-
-
Alvaro Herrera authored
-
- Sep 08, 2009
-
-
Tom Lane authored
build actually attempts to advertise itself via Bonjour. Formerly it always did so, which meant that packagers had to decide for their users whether this behavior was wanted or not. The default is "off" to be on the safe side, though this represents a change in the default behavior of a Bonjour-enabled build. Per discussion.
-