aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Add missing part of replication role docsMagnus Hagander2011-01-03
| | | | Noted by Peter E.
* perltidy run on the MSVC build systemMagnus Hagander2011-01-03
| | | | | Forgot this with previuos commit, line it up so it's easier to submit (readable) patches against the MSVC build system.
* Implement remaining fields of information_schema.sequences viewPeter Eisentraut2011-01-02
| | | | | | | | | 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.
* Fix typo.Robert Haas2011-01-02
| | | | Noted by Magnus Hagander.
* Basic foreign table support.Robert Haas2011-01-01
| | | | | | | | | | | 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
* Minor wordsmithing.Robert Haas2011-01-01
| | | | As suggested by Tom Lane, in response to a gripe from Leslie S Satenstein.
* Fix pg_dump support for security labels on columns.Robert Haas2011-01-01
| | | | Along the way, correct an erroneous comment.
* Allow casting a table's row type to the table's supertype if it's a typed tablePeter Eisentraut2011-01-01
| | | | | This is analogous to the existing facility that allows casting a row type to a supertable's row type.
* Add #include <time.h> to pg_ctl.c to fix compiler warning.Bruce Momjian2011-01-01
|
* Stamp copyrights for year 2011.Bruce Momjian2011-01-01
|
* Furter pg_upgrade optimizations to reduce function call argument count.Bruce Momjian2011-01-01
|
* In pg_upgrade, remove use of whichCluster, and just pass old/new clusterBruce Momjian2011-01-01
| | | | | | | 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.
* In pg_upgrade, rename "CLUSTERNAME" to "CLUSTER_NAME".Bruce Momjian2010-12-31
|
* Include the first valid listen address in pg_ctl to improve server startBruce Momjian2010-12-31
| | | | | "wait" detection and add postmaster start time to help determine if the postmaster is actually using the specified data directory.
* Invert and rename flag variable to improve code readability.Tom Lane2010-12-31
| | | | No change in functionality. Per discussion with Robert.
* Move symbols for ExecMergeJoin's state machine into nodeMergejoin.c.Tom Lane2010-12-30
| | | | | There's no reason for these values to be known anywhere else. After doing this, executor/execdefs.h is vestigial and can be removed.
* Support RIGHT and FULL OUTER JOIN in hash joins.Tom Lane2010-12-30
| | | | | | | | | | | | | | | | | | | | | | 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.
* Remove tabs in SGMLPeter Eisentraut2010-12-30
|
* Avoid unnecessary public struct declaration in slru.hAlvaro Herrera2010-12-30
| | | | | | | | 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
* Doc wording improvement: taken -> acceptedBruce Momjian2010-12-29
| | | | with time zone</type>.) <type>timestamptz</type> is accepted as an
* Improve pg_upgrade's checks for required executables.Tom Lane2010-12-29
| | | | | | | | | | | | | | 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.
* Bump XLOG_PAGE_MAGIC.Robert Haas2010-12-29
| | | | | | The unlogged tables patch (commit 53dbc27c62d8e1b6c5253feba04a5094cb8fe046, 2010-12-29) should have done this, since it changes the format of an XLOG_SMGR_CREATE record.
* Support unlogged tables.Robert Haas2010-12-29
| | | | | | | 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.
* Add REPLICATION privilege for ROLEsMagnus Hagander2010-12-29
| | | | | | | | | | | 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.
* Avoid unexpected conversion overflow in planner for distant date values.Tom Lane2010-12-28
| | | | | | | | | | | | | | 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.
* Reclassify DEFAULT as a column_constraint item in the CREATE TABLE syntax.Tom Lane2010-12-28
| | | | | | | | | | | | | | 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.
* No release notes update, just advance the dateREL9_1_ALPHA3Peter Eisentraut2010-12-28
|
* Fix ill-advised placement of PGRES_COPY_BOTH enum value.Tom Lane2010-12-28
| | | | | It must be added at the end of the ExecStatusType enum to avoid ABI breakage compared to previous libpq versions. Noted by Magnus.
* Another fix for larger postmaster.pid files.Bruce Momjian2010-12-28
|
* Fix list of functions that are restricted to superusersMagnus Hagander2010-12-28
| | | | | Move the list of what's restricted to superusers into the table itself, so it doesn't get missed again.
* Fix code to properly pull out shared memory key now that theBruce Momjian2010-12-27
| | | | | postmaster.pid file is larger than in previous major versions. This is a bug introduced when I added lines to the file recently.
* Mark unaccent functions as STABLE, rather than defaulting to VOLATILE.Bruce Momjian2010-12-27
|
* Update SGML docs describing the contents of the postmaster.pid file,Bruce Momjian2010-12-27
| | | | per change to the file for pg_ctl.
* Remove -fno-operator-names switch from cpluspluscheck.Tom Lane2010-12-27
| | | | No longer needed now that bitand() and bitor() have been renamed.
* Rename the C functions bitand(), bitor() to bit_and(), bit_or().Tom Lane2010-12-27
| | | | | | | | | 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.
* Rearrange cpluspluscheck to check just one .h file at a time.Tom Lane2010-12-27
| | | | | | | | | | | 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.
* Fix failure of executor/hashjoin.h to compile standalone.Tom Lane2010-12-27
| | | | Noted while experimenting with cpluspluscheck.
* Tweak cpluspluscheck to avoid directly #include'ing gram.h.Tom Lane2010-12-27
| | | | | 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.
* Fix ill-chosen use of "private" as an argument and struct field name.Tom Lane2010-12-27
| | | | | | "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.
* Break up long line, per Leslie S Satenstein.Alvaro Herrera2010-12-27
|
* Corrections to patch adding SQL/MED error codes.Robert Haas2010-12-26
| | | | | | | My previous commit, 85cff3ce7f360d139d87aee836d75a6202fee066 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.
* Only build in crashdump support on Windows if there's a working dbghelp.h.Andrew Dunstan2010-12-26
|
* Add foreign data wrapper error code values for SQL/MED.Robert Haas2010-12-25
| | | | Extracted from a much larger patch by Shigeru Hanada.
* Correct spelling: longjump() -> longjmp().Robert Haas2010-12-24
|
* Fix grammarPeter Eisentraut2010-12-24
|
* Allow vpath builds and regression tests to succeed on Mingw. Backpatch to ↵Andrew Dunstan2010-12-24
| | | | release 8.4 - earlier releases would require more changes and it's not worth the trouble.
* Remove quotes from boolean recovery.conf.sample parameters, now that theBruce Momjian2010-12-24
| | | | | quotes are not required. This now matches postgresql.conf's specification of booleans.
* Improve "pg_ctl -w start" server detection by writing the postmasterBruce Momjian2010-12-24
| | | | | port and socket directory into postmaster.pid, and have pg_ctl read from that file, for use by PQping().
* Move the documentation of --no-security-label to a more sensible placePeter Eisentraut2010-12-24
| | | | | The order on the pg_dump/pg_dumpall man pages is not very strict, but surely putting it under connection options was wrong.
* Release notes for 9.1alpha3Peter Eisentraut2010-12-24
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 04:54:10 +0000