- 20 10月, 2006 6 次提交
-
-
由 Tom Lane 提交于
be NULL ... seems an unsafe assumption.
-
由 Tom Lane 提交于
if available (which it usually should be), during processing of Bind and Execute protocol messages. This improves usefulness of log_min_error_statement logging for extended query protocol.
-
由 Tom Lane 提交于
from Magnus that MSVC complains about this.
-
由 Neil Conway 提交于
-
由 Tom Lane 提交于
per Magnus.
-
由 Tom Lane 提交于
sin_port in the returned IP address struct when servname is NULL. This has been observed to cause failure to bind the stats collection socket, and could perhaps cause other issues too. Per reports from Brad Nicholson and Chris Browne.
-
- 19 10月, 2006 2 次提交
-
-
由 Tom Lane 提交于
that conflict with the OID that we want to use for the new database. This avoids the risk of trying to remove files that maybe we shouldn't remove. Per gripe from Jon Lapham and subsequent discussion of 27-Sep.
-
由 Tom Lane 提交于
timezone actually has a daylight-savings rule. This avoids breaking cases that used to work because they went through the DecodePosixTimezone code path. Per contrib regression failures (mea culpa for not running those yesterday...). Also document the already-applied change to allow GMT offsets up to 14 hours.
-
- 18 10月, 2006 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
input routines. Remove the former "DecodePosixTimezone" function in favor of letting the zic code handle POSIX-style zone specs (see tzparse()). In particular this means that "PST+3" now means the same as "-03", whereas it used to mean "-11" --- the zone abbreviation is effectively just a noise word in this syntax. Make sure that all named and POSIX-style zone names will be parsed as a single token. Fix long-standing bogosities in printing and input of fractional-hour timezone offsets (since the tzparse() code will accept these, we'd better make 'em work). Also correct an error in the original coding of the zic-zone-name patch: in "timestamp without time zone" input, zone names are supposed to be allowed but ignored, but the coding was such that the zone changed the interpretation anyway.
-
由 Bruce Momjian 提交于
Wheeler.
-
- 17 10月, 2006 10 次提交
-
-
由 Bruce Momjian 提交于
related to website development and change the link to the FAQ_DEV.html. Devrim GUNDUZ
-
由 Bruce Momjian 提交于
Michael Paesold
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
example SET TIME ZONE 'america/new_york' works now. This seems a good idea on general user-friendliness grounds, and is part of the solution to the timestamp-input parsing problems I noted recently.
-
由 Bruce Momjian 提交于
Michael Paesold
-
由 Bruce Momjian 提交于
Michael Glaesemann
-
由 Bruce Momjian 提交于
Devrim GUNDUZ
-
由 Bruce Momjian 提交于
Update find_gt_lt to allow grep parameters to be passed into it.
-
由 Peter Eisentraut 提交于
Also cut back on excessive use of *** to decorate configure error messages. If it's an error message, you are sure to see it without any decoration.
-
- 16 10月, 2006 2 次提交
-
-
由 Tom Lane 提交于
modules; the first try was not usable in EXEC_BACKEND builds (e.g., Windows). Instead, just provide some entry points to increase the allocation requests during postmaster start, and provide a dedicated LWLock that can be used to synchronize allocation operations performed by backends. Per discussion with Marc Munro.
-
由 Tom Lane 提交于
are marked as UTF8 when the database encoding is UTF8. This should avoid inconsistencies like that exhibited in bug #2683 from Vitali Stupin.
-
- 15 10月, 2006 3 次提交
-
-
由 Bruce Momjian 提交于
Jun Kuwamura
-
由 Bruce Momjian 提交于
channel to the lists of IRC channels, fixes a typo in the OID's question, and corrects the PGCluster's project name. Euler Taveira de Oliveira
-
由 Tom Lane 提交于
one of the program's core data structures, make use of the existing ability to selectively exclude TOC items by ID. Slightly more code but much less likely to create future maintenance problems.
-
- 14 10月, 2006 3 次提交
-
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
and neither is "|" or "\|" in basic regular expressions.
-
由 Bruce Momjian 提交于
Jun Kuwamura
-
- 13 10月, 2006 10 次提交
-
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
Hiroshi Saito
-
由 Teodor Sigaev 提交于
1) pgwin32_waitforsinglesocket(): WaitForMultipleObjectsEx now called with finite timeout (100ms) in case of FP_WRITE and UDP socket. If timeout occurs then pgwin32_waitforsinglesocket() tries to write empty packet goes to WaitForMultipleObjectsEx again. 2) pgwin32_send(): add loop around WSASend and pgwin32_waitforsinglesocket(). The reason is: for overlapped socket, 'ok' result from pgwin32_waitforsinglesocket() isn't guarantee that socket is still free, it can become busy again and following WSASend call will fail with WSAEWOULDBLOCK error. See http://archives.postgresql.org/pgsql-hackers/2006-10/msg00561.php
-
由 Bruce Momjian 提交于
< o Issue a notice if CREATE TABLE ... ON COMMIT { DELETE ROWS | < DROP } is issued outside a multi-statement transaction
-
由 Bruce Momjian 提交于
> o Issue a notice if CREATE TABLE ... ON COMMIT { DELETE ROWS | > DROP } is issued outside a multi-statement transaction
-
由 Neil Conway 提交于
Continuous Archiving. Plenty of editorial work remains...
-
由 Tom Lane 提交于
-
由 Neil Conway 提交于
to the discussion of the "--with-ldap" configure option. Patch from Albe Laurenz.
-
由 Tom Lane 提交于
rows --- if the surrounding query queued any trigger events between the rows, the events would be fired at the wrong time, leading to bizarre behavior. Per report from Merlin Moncure. This is a simple patch that should solve the problem fully in the back branches, but in HEAD we also need to consider the possibility of queries with RETURNING clauses. Will look into a fix for that separately.
-
- 12 10月, 2006 1 次提交
-
-
由 Tom Lane 提交于
redefined-macro warnings on some platforms. Per gripe from Hiroshi Saito.
-