Log Message:
---
Bump version
Modified Files:
--
wizard:
CMakeLists.txt (r1.28 -> r1.29)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackbuilder/wizard/CMakeLists.txt?r1=1.28&r2=1.29)
StackBuilder.rc (r1.1 -> r1.2)
(http://cvs.pgfoundry.o
pg_dump: Add gettext plural support to error message
Branch
--
REL9_1_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/10ff8f98a0df59d0ad5d162cd88a0c687c3a5920
Modified Files
--
src/bin/pg_dump/pg_dump.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
pg_dump: Add gettext plural support to error message
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/9922fc5f9f02e9d1653d08b0e62cefa8560425be
Modified Files
--
src/bin/pg_dump/pg_dump.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
--
Se
Peter Eisentraut writes:
> pg_dump: Add gettext plural support to error message
Er, what for? The case n=1 is explicitly excluded.
I'm not sure this message is even worth translating, since it should
be a can't-happen case, but making the translators do it twice is surely
unnecessary.
On tis, 2011-11-29 at 14:48 -0500, Tom Lane wrote:
> Peter Eisentraut writes:
> > pg_dump: Add gettext plural support to error message
>
> Er, what for? The case n=1 is explicitly excluded.
Because other languages have more than one plural form. It's the same
reason why we have
if (ntups
When a row fails a CHECK constraint, show row's contents in errdetail.
This should make it easier to identify which row is problematic when an
insert or update is processing many rows.
The formatting is similar to that for unique-index violation messages,
except that we limit field widths to 64 b
Suggest configure options for server developers.
Greg Smith
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/b60f37bf44c248189ed8e4d925cd8e45308d54f8
Modified Files
--
doc/src/sgml/installation.sgml |9 +
1 files changed, 9 insertions(+), 0 del
Simplify the pg_dump/pg_restore error reporting macros, and allow
pg_dumpall to use the same memory allocation functions as the others.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/8b08deb0d1ee04a82130e640e48e302a3456817a
Modified Files
--
src/bin/pg_d
When a row fails a not-null constraint, show row's contents in errdetail.
Simple extension of previous patch for CHECK constraints.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/f225e4bc54df77e766b0edcffacb865648b099a3
Modified Files
--
src/backend/exe
In docs, suggest "-O0 -g" only if using a debugger.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/2ff36abeec948899b9a51d1c945e9fbe85e056d5
Modified Files
--
doc/src/sgml/installation.sgml |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--
Clean up after recent pg_dump patches.
Fix entirely broken handling of va_list printing routines, update some
out-of-date comments, fix some bogus inclusion orders, fix NLS declarations,
fix missed realloc calls.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/0195e5
Change installation docs to mention general debugging options.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/99f5e47df5d04670be2fb5d575d6dc294a312eea
Modified Files
--
doc/src/sgml/installation.sgml |4 ++--
1 files changed, 2 insertions(+), 2 deleti
Prevent autovacuum transactions from running in serializable mode.
Force the transaction isolation level to READ COMMITTED in autovacuum
worker and launcher processes. There is no benefit to using a higher
isolation level, and doing so could result in delaying foreground
transactions (or maybe ev
Prevent autovacuum transactions from running in serializable mode.
Force the transaction isolation level to READ COMMITTED in autovacuum
worker and launcher processes. There is no benefit to using a higher
isolation level, and doing so could result in delaying foreground
transactions (or maybe ev
On 11/29/2011 10:40 PM, Tom Lane wrote:
Prevent autovacuum transactions from running in serializable mode.
Force the transaction isolation level to READ COMMITTED in autovacuum
worker and launcher processes. There is no benefit to using a higher
isolation level, and doing so could result in d
On 11/29/2011 11:03 PM, Andrew Dunstan wrote:
Looks like this broke the buildfarm.
Actually, it was the pg_dump cleanup.
I clicked the wrong message.
cheers
andrew
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http:/
Andrew Dunstan writes:
> On 11/29/2011 11:03 PM, Andrew Dunstan wrote:
>> Looks like this broke the buildfarm.
> Actually, it was the pg_dump cleanup.
Huh, my compiler didn't complain. Will fix, thanks!
regards, tom lane
--
Sent via pgsql-committers mailing list (pgsq
Move EXTRA_CLEAN to where it actually works.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/9c6aa8cca0c8b2d46a174ec5171c2cf0aa97b2d0
Modified Files
--
contrib/pg_upgrade/Makefile |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
--
Sent via
Remove duplicate definition of 'progname'.
Per buildfarm.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/be2f909200ece7985d60848797c3eb07f9d1b995
Modified Files
--
src/bin/pg_dump/pg_dumpall.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
Strip file names reported in error messages in vpath builds
In vpath builds, the __FILE__ macro that is used in verbose error
reports contains the full absolute file name, which makes the error
messages excessively verbose. So keep only the base name, thus
matching the behavior of non-vpath build
Strip file names reported in error messages in vpath builds
In vpath builds, the __FILE__ macro that is used in verbose error
reports contains the full absolute file name, which makes the error
messages excessively verbose. So keep only the base name, thus
matching the behavior of non-vpath build
Strip file names reported in error messages in vpath builds
In vpath builds, the __FILE__ macro that is used in verbose error
reports contains the full absolute file name, which makes the error
messages excessively verbose. So keep only the base name, thus
matching the behavior of non-vpath build
Strip file names reported in error messages in vpath builds
In vpath builds, the __FILE__ macro that is used in verbose error
reports contains the full absolute file name, which makes the error
messages excessively verbose. So keep only the base name, thus
matching the behavior of non-vpath build
Strip file names reported in error messages in vpath builds
In vpath builds, the __FILE__ macro that is used in verbose error
reports contains the full absolute file name, which makes the error
messages excessively verbose. So keep only the base name, thus
matching the behavior of non-vpath build
Strip file names reported in error messages in vpath builds
In vpath builds, the __FILE__ macro that is used in verbose error
reports contains the full absolute file name, which makes the error
messages excessively verbose. So keep only the base name, thus
matching the behavior of non-vpath build
Tweak previous patch to ensure edata->filename always gets initialized.
On a platform that isn't supplying __FILE__, previous coding would either
crash or give a stale result for the filename string. Not sure how likely
that is, but the original code catered for it, so let's keep doing so.
Branc
Tweak previous patch to ensure edata->filename always gets initialized.
On a platform that isn't supplying __FILE__, previous coding would either
crash or give a stale result for the filename string. Not sure how likely
that is, but the original code catered for it, so let's keep doing so.
Branc
Tweak previous patch to ensure edata->filename always gets initialized.
On a platform that isn't supplying __FILE__, previous coding would either
crash or give a stale result for the filename string. Not sure how likely
that is, but the original code catered for it, so let's keep doing so.
Branc
Tweak previous patch to ensure edata->filename always gets initialized.
On a platform that isn't supplying __FILE__, previous coding would either
crash or give a stale result for the filename string. Not sure how likely
that is, but the original code catered for it, so let's keep doing so.
Branc
Tweak previous patch to ensure edata->filename always gets initialized.
On a platform that isn't supplying __FILE__, previous coding would either
crash or give a stale result for the filename string. Not sure how likely
that is, but the original code catered for it, so let's keep doing so.
Branc
Tweak previous patch to ensure edata->filename always gets initialized.
On a platform that isn't supplying __FILE__, previous coding would either
crash or give a stale result for the filename string. Not sure how likely
that is, but the original code catered for it, so let's keep doing so.
Branc
31 matches
Mail list logo
