- 27 1月, 2011 10 次提交
-
-
由 Bruce Momjian 提交于
paragraphs, per suggestion from Dan Birken.
-
由 Tom Lane 提交于
In the case where the initial call of systable_getnext_ordered() returned NULL, this function would nonetheless call it again. That's undefined behavior that only by chance failed to not give visibly incorrect results. Put an if-test around the final loop to prevent that, and in passing improve some comments. No back-patch since there's no actual failure. Per report from YAMAMOTO Takashi.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
Synchronize pg_config.h.in with configure.in (someone must have forgotten to run autoheader or autoreconf), and clean up some spurious change in configure introduced by the last commit there.
-
由 Peter Eisentraut 提交于
It is redundant, given the error context. Jan Urbański
-
由 Peter Eisentraut 提交于
Use the built-in TypeError, not SPIError, for errors having to do with argument counts or types. Use SPIError, not simply plpy.Error, for errors in PLy_spi_execute_plan. Finally, do not set a Python exception if PyArg_ParseTuple failed, as it already sets the correct exception. Jan Urbański
-
由 Peter Eisentraut 提交于
The temporarily broken plpython_unicode test shows a case where this is used. Do remaining fix-ups on the expected files at the same time.
-
由 Peter Eisentraut 提交于
Older versions of GCC appear to report these with the current standard option set, newer versions need -Wformat-security.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 26 1月, 2011 12 次提交
-
-
由 Bruce Momjian 提交于
sections, rather than just calling it "/contrib/module_name". Also update pg_test_fsync build instructions now that it is in /contrib.
-
由 Bruce Momjian 提交于
non-durable items, per Robert Haas.
-
由 Itagaki Takahiro 提交于
-
由 Robert Haas 提交于
Noah Misch, slightly revised.
-
由 Robert Haas 提交于
The previous coding prevented ALTER TABLE .. ADD COLUMN from being used with a non-NULL default in situations where the table's rowtype was being used elsewhere. But this is a completely arbitrary restriction since you could do the same operation in multiple steps (add the column, add the default, update the table). Inspired by a patch from Noah Misch, though I didn't use his code.
-
由 Bruce Momjian 提交于
always 8k writes, per suggestion from Tom. Also adjust open_sync output layout.
-
由 Bruce Momjian 提交于
Robvert Haas.
-
由 Robert Haas 提交于
The latter is the correct name of the operation to change the data type of a column. Noah Misch
-
由 Tom Lane 提交于
We used to do that on pg_listener, but pg_listener is no more. Also add a bit more documentation for ShareRowExclusive mode.
-
由 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 11 次提交
-
-
由 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
-