- 26 1月, 2011 3 次提交
-
-
由 Robert Haas 提交于
Noah Misch
-
由 Tom Lane 提交于
There isn't any need to track this state on a table-wide basis, and trying to do so introduces undesirable semantic fuzziness. Move the flag to pg_index, where it clearly describes just a single index and can be immutable after index creation.
-
由 Tom Lane 提交于
This feature allows a unique or pkey constraint to be created using an already-existing unique index. While the constraint isn't very functionally different from the bare index, it's nice to be able to do that for documentation purposes. The main advantage over just issuing a plain ALTER TABLE ADD UNIQUE/PRIMARY KEY is that the index can be created with CREATE INDEX CONCURRENTLY, so that there is not a long interval where the table is locked against updates. On the way, refactor some of the code in DefineIndex() and index_create() so that we don't have to pass through those functions in order to create the index constraint's catalog entries. Also, in parse_utilcmd.c, pass around the ParseState pointer in struct CreateStmtContext to save on notation, and add error location pointers to some error reports that didn't have one before. Gurjeet Singh, reviewed by Steve Singer and Tom Lane
-
- 25 1月, 2011 7 次提交
-
-
由 Magnus Hagander 提交于
Fujii Masao
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
it is 8k as expected.
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
This option was recently introduced, but the documentation in help.c was not updated.
-
由 Peter Eisentraut 提交于
This way errors from fetching tuples are correctly reported as errors in the SPI call. While at it, avoid palloc(0). Jan Urbański
-
由 Peter Eisentraut 提交于
Instead of checking whether the arglist is NULL and then if its length is 0, do it in one step, and outside of the try/catch block. Jan Urbański
-
- 24 1月, 2011 19 次提交
-
-
由 Robert Haas 提交于
Thom Brown and Robert Haas
-
由 Heikki Linnakangas 提交于
against 9.0 servers.
-
由 Magnus Hagander 提交于
In passing, change exclusion in the build to follow the same pattern as other always-excluded modules.
-
由 Heikki Linnakangas 提交于
Itagaki Takahiro
-
由 Robert Haas 提交于
Joey Adams
-
由 Robert Haas 提交于
-
由 Robert Haas 提交于
Robert Haas, with a few suggestions from Thom Brown
-
由 Robert Haas 提交于
This is still pretty rough - among other things, the documentation needs work, and the messages need a visit from the style police - but this gets the basic framework in place. KaiGai Kohei
-
由 Magnus Hagander 提交于
While doing this, also move base backup options into a struct instead of increasing the number of parameters to multiple functions for each new option.
-
由 Magnus Hagander 提交于
-
由 Heikki Linnakangas 提交于
with the 'tar' format, in that untarring a tar format archive produces a valid directory format archive. Joachim Wieland and Heikki Linnakangas
-
由 Tom Lane 提交于
The target of sscanf with a %o format had better be of integer width, but "mode_t" conceivably isn't that. Another compiler warning seen only on some platforms; this one I think is potentially a real bug and not just a warning.
-
由 Tom Lane 提交于
Include the lefttype/righttype columns explicitly (instead of assuming the reader can deduce them from the operator or function description), and move the operator or function description to the end of the string, to make it clearer that it's a referenced object and not the amop or amproc item itself. Per extensive discussion of Andreas Karlsson's original patch. Andreas Karlsson, Tom Lane
-
由 Tom Lane 提交于
This reverts commit 740e54ca, which seems to have tickled an optimization bug in gcc 4.5.x, as reported upstream at https://bugzilla.redhat.com/show_bug.cgi?id=671899 Since this patch had no purpose beyond code beautification, it's not worth expending a lot of effort to look for another workaround.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Andrew Dunstan 提交于
-
由 Magnus Hagander 提交于
Per buildfarm.
-
由 Magnus Hagander 提交于
-
- 23 1月, 2011 11 次提交
-
-
由 Magnus Hagander 提交于
Per buildfarm failure.
-
由 Magnus Hagander 提交于
This tool makes it possible to do the pg_start_backup/ copy files/pg_stop_backup step in a single command. There are still some steps to be done before this is a complete backup solution, such as the ability to stream the required WAL logs, but it's still usable, and could do with some buildfarm coverage. In passing, make the checkpoint request optionally fast instead of hardcoding it. Magnus Hagander, reviewed by Fujii Masao and Dimitri Fontaine
-
由 Robert Haas 提交于
As in commit fb4c5d27 on 2011-01-21, this avoids spurious debug messages and allows idempotent changes at any time. Along the way, make assign_XactIsoLevel allow idempotent changes even when not within a subtransaction, to be consistent with the new coding of assign_transaction_read_only and because there's no compelling reason to do otherwise. Kevin Grittner, with some adjustments.
-
由 Tom Lane 提交于
It's not clear to me what should happen to the other plpython_unicode variant expected files, but this patch gets things passing on my own machines and at least some of the buildfarm.
-
由 Tom Lane 提交于
If wal_buffers is initially set to -1 (which is now the default), it's replaced by 1/32nd of shared_buffers, with a minimum of 8 (the old default) and a maximum of the XLOG segment size. The allowed range for manual settings is still from 4 up to whatever will fit in shared memory. Greg Smith, with implementation correction by me.
-
由 Tom Lane 提交于
Not sure why I'm seeing this on Fedora 14 and not earlier versions. Seems like a regression that gcc no longer knows that DIE() doesn't return. Still, adding a dummy return is harmless enough.
-
由 Tom Lane 提交于
It appears that gcc 4.5 can issue such warnings for whole structs, not just scalar variables as in the past. Refactor some pg_dump code slightly so that the OutputContext local variables are always initialized, even if they won't be used. It's cheap enough to not be worth worrying about.
-
由 Peter Eisentraut 提交于
Global error handling led to confusion and was hard to manage. With this change, errors from PostgreSQL are immediately reported to Python as exceptions. This requires setting a Python exception after reporting the caught PostgreSQL error as a warning, because PLy_elog destroys the Python exception state. Ideally, all places where PostgreSQL errors need to be reported back to Python should be wrapped in subtransactions, to make going back to Python from a longjmp safe. This will be handled in a separate patch. Jan Urbański
-
由 Tom Lane 提交于
Reduce #includes to minimum actually needed; in particular include postgres_fe.h not postgres.h, so as to stop build failures on some platforms. Use get_progname() instead of hardwired program name; improve error checking for command line syntax; bring error messages into line with style guidelines; include strerror result in die() cases.
-
由 Tom Lane 提交于
Per buildfarm.
-
由 Magnus Hagander 提交于
-