This patch has a fix for a 'thought-o' in the docs.
Gavin
Index: doc/src/sgml/ref/alter_index.sgml
===
RCS file: /usr/local/cvsroot/pgsql-server/doc/src/sgml/ref/alter_index.sgml,v
retrieving revision 1.1
diff -2 -c -r1.1
Gavin Sherry wrote:
Index: src/bin/psql/tab-complete.c
===
RCS file: /usr/local/cvsroot/pgsql-server/src/bin/psql/tab-complete.c,v
retrieving revision 1.109
diff -2 -c -r1.109 tab-complete.c
*** src/bin/psql/tab-complete.c 28 Jul
Oops.
Too much with the ol' cut and paste.
I'm happy to send an updated patch but perhaps the committer, assuming the
patch is accepted, would be kind enough to update for me.
Thanks for reviewing.
Gavin
On Fri, 13 Aug 2004, Stefan Kaltenbrunner wrote:
Gavin Sherry wrote:
Index:
[redirecting]
I have abstracted this problem, and we definitely have a newline bug
that has to be fixed, IMNSHO.
Attached are 2 scripts that are identical except that one has DOS-style
line endings and one has Unix style line endings. The DOS-style just
fails miserably with no warning. It's
Martin Münstermann wrote:
Hi!
Martin M?nstermann wrote:
OK, we now have thread compile failure reports on Debian and Slackware.
The config/acx_pthread.m4 script basically tests these:
acx_pthread_flags=3Dpthreads none -Kthread -kthread lthread -pthread
-pthreads
OK, we now have thread compile failure reports on Debian and Slackware.
The config/acx_pthread.m4 script basically tests these:
acx_pthread_flags=3Dpthreads none -Kthread -kthread lthread -pthread
-pthreads -mthreads pthread --thread-safe -mt pthread-config
=09
in that
Am Donnerstag, 12. August 2004 16:26 schrieb Serguei Mokhov:
A new batch of translated messges for the backend.
Please apply to both 7.4 and 8.0.
Done.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2:
Am Donnerstag, 12. August 2004 16:23 schrieb Serguei Mokhov:
These are fully translated. Some messages
were tweaked, with some errors fixed.
Please install for 8.0.
Done.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of
Kind people,
The enclose patch clarifies and makes a more useful example for the
Global Values in PL/Perl section of the documents.
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fetter.org/
phone: +1 510 893 6100 mobile: +1 415 235 3778
Remember to vote!
? plperl.diff
Index: plperl.sgml
Here's the manual pages that went missing a few weeks backI asked my
secretary to post them through, and she had some success, though that looks
like they were weeded out as spam/viruses.
My continued absence is the result of a truck's surprise attempt to test my
personal capability for
Andrew Dunstan [EMAIL PROTECTED] writes:
The attached patch appears to solve the problem. However, while it
makes us conform to the first sentence below from the docs, it doesn't
comply with the second. Not sure what to do about that. Maybe there's
a better solution?
Attached patch seems
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Now, if you say people will rarely turn archiving on/off, then one
parameter seems to make more sense.
I really can't envision a situation where people would do that. If you
need PITR at all then you need it 24x7.
I agree.
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
The attached patch appears to solve the problem. However, while it
makes us conform to the first sentence below from the docs, it doesn't
comply with the second. Not sure what to do about that. Maybe there's
a better solution?
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
I would opt to make enabling/disabling archive_command require a postmaster
restart. That way there would be no capability to take advantage of the
incentive to turn it on/off.
We're generally not in the habit of making GUC parameters more rigid
than
Andrew Dunstan [EMAIL PROTECTED] writes:
Should it be backported for the upcoming stable release(s)? Bruce and I
were discussing this earlier.
Probably a good idea, since we do support psql on Windows even in the
older releases.
My personal opinion is to back-port only as far as 7.4, but if
Tom Lane said:
Andrew Dunstan [EMAIL PROTECTED] writes:
Should it be backported for the upcoming stable release(s)? Bruce and
I were discussing this earlier.
Probably a good idea, since we do support psql on Windows even in the
older releases.
My personal opinion is to back-port only as
Andrew Dunstan [EMAIL PROTECTED] writes:
No, I think 7.4 should do. 7.3 users will still have the dos2unix workaround
available. Are you going to do the 7.4 patch, or do you need me to? I
normally only keep a HEAD tree checked out. A quick look at the cvsweb diffs
suggests the patch should
17 matches
Mail list logo
