On 26 February 2013 16:29, Heikki Linnakangas wrote:
> On 26.02.2013 18:03, Thom Brown wrote:
>>
>> On 20 February 2013 15:14, Heikki Linnakangas
>> wrote:
>>>
>>> Fix pg_dumpall with database names containing =
>>>
>>> If a database name contained a '=' character, pg_dumpall failed. The
>>> probl
Log Message:
---
[#1011310] Command timeouts after the first are not handled. Applied patch
[#1011311]. Thank you, Evan Martin, for bug report and patch!
When a command inside a transaction times out the caller may roll back to a
savepoint and try again. This works OK the first time. Th
Add missing error check in regexp parser.
parseqatom() failed to check for an error return (NULL result) from its
recursive call to parsebranch(), and in consequence could crash with a
null-pointer dereference after an error return. This bug has been there
since day one, but wasn't noticed before
Add missing error check in regexp parser.
parseqatom() failed to check for an error return (NULL result) from its
recursive call to parsebranch(), and in consequence could crash with a
null-pointer dereference after an error return. This bug has been there
since day one, but wasn't noticed before
Add missing error check in regexp parser.
parseqatom() failed to check for an error return (NULL result) from its
recursive call to parsebranch(), and in consequence could crash with a
null-pointer dereference after an error return. This bug has been there
since day one, but wasn't noticed before
Add missing error check in regexp parser.
parseqatom() failed to check for an error return (NULL result) from its
recursive call to parsebranch(), and in consequence could crash with a
null-pointer dereference after an error return. This bug has been there
since day one, but wasn't noticed before
Add missing error check in regexp parser.
parseqatom() failed to check for an error return (NULL result) from its
recursive call to parsebranch(), and in consequence could crash with a
null-pointer dereference after an error return. This bug has been there
since day one, but wasn't noticed before
Add support for piping COPY to/from an external program.
This includes backend "COPY TO/FROM PROGRAM '...'" syntax, and corresponding
psql \copy syntax. Like with reading/writing files, the backend version is
superuser-only, and in the psql version, the program is run in the client.
In the passin
On 27 February 2013 16:22, Heikki Linnakangas wrote:
> Add support for piping COPY to/from an external program.
>
> This includes backend "COPY TO/FROM PROGRAM '...'" syntax, and corresponding
> psql \copy syntax. Like with reading/writing files, the backend version is
> superuser-only, and in the
Add standard file header comment to quotes.c.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/5ddf38f21d3f34c794de2d1c9b61ba92a7d6f39c
Modified Files
--
src/port/quotes.c | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
--
Sent
Cannot use WL_SOCKET_WRITEABLE without WL_SOCKET_READABLE.
In copy-out mode, the frontend should not send any messages until the
backend has finished streaming, by sending a CopyDone message. I'm not sure
if it would be legal for the client to send a new query before receiving the
CopyDone message
On 27.02.2013 18:35, Thom Brown wrote:
On 27 February 2013 16:22, Heikki Linnakangas wrote:
Add support for piping COPY to/from an external program.
This includes backend "COPY TO/FROM PROGRAM '...'" syntax, and corresponding
psql \copy syntax. Like with reading/writing files, the backend vers
Fix typo in "pg_xlogdump --help" and error message.
Fujii Masao and me.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/26b45dc54f379c4e7b44b308584dc14d0ed17482
Modified Files
--
contrib/pg_xlogdump/pg_xlogdump.c |4 ++--
1 files changed, 2 insertions
Fix MSVC build.
The new file in src/port needs to be listed in Mkvcbuild.pm as well.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/f70b1b274824e5116c8e993d274629d3934b3978
Modified Files
--
src/tools/msvc/Mkvcbuild.pm |2 +-
1 files changed, 1 inser
On 27 February 2013 19:12, Heikki Linnakangas wrote:
> On 27.02.2013 18:35, Thom Brown wrote:
>>
>> On 27 February 2013 16:22, Heikki Linnakangas
>> wrote:
>>>
>>> Add support for piping COPY to/from an external program.
>>>
>>> This includes backend "COPY TO/FROM PROGRAM '...'" syntax, and
>>> co
On 27.02.2013 21:46, Thom Brown wrote:
On 27 February 2013 19:12, Heikki Linnakangas wrote:
(I note that there is a spurious "the" in my wording, though. Should be
"..., such as SELinux")
My version also added a "the" before "operating system's". So I guess
it's just a case of moving "the" f
Remove spurious "the", and add a missing one.
Thom Brown and me.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/7d6b8f7158f0ea2e55b42c1db1d31991e3c67572
Modified Files
--
doc/src/sgml/ref/copy.sgml |2 +-
1 files changed, 1 insertions(+), 1 deletions
17 matches
Mail list logo
