- 02 1月, 2011 10 次提交
-
-
由 Peter Eisentraut 提交于
Add new function pg_sequence_parameters that returns a sequence's start, minimum, maximum, increment, and cycle values, and use that in the view. (bug #5662; design suggestion by Tom Lane) Also slightly adjust the view's column order and permissions after review of SQL standard.
-
由 Robert Haas 提交于
Noted by Magnus Hagander.
-
由 Robert Haas 提交于
Foreign tables are a core component of SQL/MED. This commit does not provide a working SQL/MED infrastructure, because foreign tables cannot yet be queried. Support for foreign table scans will need to be added in a future patch. However, this patch creates the necessary system catalog structure, syntax support, and support for ancillary operations such as COMMENT and SECURITY LABEL. Shigeru Hanada, heavily revised by Robert Haas
-
由 Robert Haas 提交于
As suggested by Tom Lane, in response to a gripe from Leslie S Satenstein.
-
由 Robert Haas 提交于
Along the way, correct an erroneous comment.
-
由 Peter Eisentraut 提交于
This is analogous to the existing facility that allows casting a row type to a supertable's row type.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
pointers, which simplifies the code. This was not possible in 9.0 because everything was in a single nested struct, but is possible now. Per suggestion from Tom.
-
- 01 1月, 2011 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
"wait" detection and add postmaster start time to help determine if the postmaster is actually using the specified data directory.
-
由 Tom Lane 提交于
No change in functionality. Per discussion with Robert.
-
- 31 12月, 2010 3 次提交
-
-
由 Tom Lane 提交于
There's no reason for these values to be known anywhere else. After doing this, executor/execdefs.h is vestigial and can be removed.
-
由 Tom Lane 提交于
This is advantageous first because it allows us to hash the smaller table regardless of the outer-join type, and second because hash join can be more flexible than merge join in dealing with arbitrary join quals in a FULL join. For merge join all the join quals have to be mergejoinable, but hash join will work so long as there's at least one hashjoinable qual --- the others can be any condition. (This is true essentially because we don't keep per-inner-tuple match flags in merge join, while hash join can do so.) To do this, we need a has-it-been-matched flag for each tuple in the hashtable, not just one for the current outer tuple. The key idea that makes this practical is that we can store the match flag in the tuple's infomask, since there are lots of bits there that are of no interest for a MinimalTuple. So we aren't increasing the size of the hashtable at all for the feature. To write this without turning the hash code into even more of a pile of spaghetti than it already was, I rewrote ExecHashJoin in a state-machine style, similar to ExecMergeJoin. Other than that decision, it was pretty straightforward.
-
由 Peter Eisentraut 提交于
-
- 30 12月, 2010 3 次提交
-
-
由 Alvaro Herrera 提交于
Instead, declare a public wrapper of the sole function using it for external callers, so that they don't have to always pass a NULL argument. Author: Kevin Grittner
-
由 Bruce Momjian 提交于
with time zone</type>.) <type>timestamptz</type> is accepted as an
-
由 Tom Lane 提交于
Don't insist on pg_dumpall and psql being present in the old cluster, since they are not needed. Do insist on pg_resetxlog being present (in both old and new), since we need it. Also check for pg_config, but only in the new cluster. Remove the useless attempt to call pg_config in the old cluster; we don't need to know the old value of --pkglibdir. (In the case of a stripped-down migration installation there might be nothing there to look at anyway, so any future change that might reintroduce that need would have to be considered carefully.) Per my attempts to build a minimal previous-version installation to support pg_upgrade.
-
- 29 12月, 2010 7 次提交
-
-
由 Robert Haas 提交于
The unlogged tables patch (commit 53dbc27c, 2010-12-29) should have done this, since it changes the format of an XLOG_SMGR_CREATE record.
-
由 Robert Haas 提交于
The contents of an unlogged table are WAL-logged; thus, they are not available on standby servers and are truncated whenever the database system enters recovery. Indexes on unlogged tables are also unlogged. Unlogged GiST indexes are not currently supported.
-
由 Magnus Hagander 提交于
This privilege is required to do Streaming Replication, instead of superuser, making it possible to set up a SR slave that doesn't have write permissions on the master. Superuser privileges do NOT override this check, so in order to use the default superuser account for replication it must be explicitly granted the REPLICATION permissions. This is backwards incompatible change, in the interest of higher default security.
-
由 Tom Lane 提交于
The "date" type supports a wider range of dates than int64 timestamps do. However, there is pre-int64-timestamp code in the planner that assumes that all date values can be converted to timestamp with impunity. Fortunately, what we really need out of the conversion is always a double (float8) value; so even when the date is out of timestamp's range it's possible to produce a sane answer. All we need is a code path that doesn't try to force the result into int64. Per trouble report from David Rericha. Back-patch to all supported versions. Although this is surely a corner case, there's not much point in advertising a date range wider than timestamp's if we will choke on such values in unexpected places.
-
由 Tom Lane 提交于
This is how it was documented originally, but several years ago somebody decided that DEFAULT isn't a type of constraint. Well, the grammar thinks it is. The documentation was wrong in two ways: it alleged that DEFAULT had to appear before any other kind of constraint, and it alleged that you can't prefix a DEFAULT clause with a "CONSTRAINT name" clause, when in fact you can. (The latter behavior probably isn't SQL-standard, but our grammar has always allowed it.) This patch responds to Fujii Masao's observation that the ALTER TABLE documentation mistakenly implied that you couldn't include DEFAULT in ALTER TABLE ADD COLUMN; though this isn't the way he proposed fixing it.
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
It must be added at the end of the ExecStatusType enum to avoid ABI breakage compared to previous libpq versions. Noted by Magnus.
-
- 28 12月, 2010 11 次提交
-
-
由 Bruce Momjian 提交于
-
由 Magnus Hagander 提交于
Move the list of what's restricted to superusers into the table itself, so it doesn't get missed again.
-
由 Bruce Momjian 提交于
postmaster.pid file is larger than in previous major versions. This is a bug introduced when I added lines to the file recently.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
per change to the file for pg_ctl.
-
由 Tom Lane 提交于
No longer needed now that bitand() and bitor() have been renamed.
-
由 Tom Lane 提交于
This is to avoid use of the C++ keywords "bitand" and "bitor" in the header file utils/varbit.h. Note the functions' SQL-level names are not changed, only their C-level names. In passing, make some comments in varbit.c conform to project-standard layout.
-
由 Tom Lane 提交于
This is slower than the original coding but avoids the problem of including files in an unpredictable order. Aside from being more trustworthy, we can get rid of some exclusions that were formerly made for what turn out to be ordering or re-inclusion problems. I also modified it to include libpq's exported files in the check. ecpg should be included as well, but I'm unclear on which ecpg .h files are meant to be included by clients.
-
由 Tom Lane 提交于
Noted while experimenting with cpluspluscheck.
-
由 Tom Lane 提交于
gram.h has ordering dependencies, which are satisfied when it's included from gramparse.h, but might not be if it's pulled in directly.
-
由 Tom Lane 提交于
"private" is a keyword in C++, so this breaks the poorly-enforced policy that header files should be include-able in C++ code. Per report from Craig Ringer and some investigation with cpluspluscheck.
-
- 27 12月, 2010 2 次提交
-
-
由 Alvaro Herrera 提交于
-
由 Robert Haas 提交于
My previous commit, 85cff3ce on 2010-12-25, failed to update errcodes.sgml or plerrcodes.h. This patch corrects that oversight, per a gripe from Tom Lane, and also corrects a typographical error.
-
- 26 12月, 2010 1 次提交
-
-
由 Andrew Dunstan 提交于
-