Log Message:
---
Fix error msg on failure to start initdb to show error description instead of just
error code.
Modified Files:
--
pginst/ca:
pginstca.c (r1.38 -> r1.39)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/ca/pginstca.c.diff?r1=
That was me adding it to the other list to get around the fact that
pgfoundry mails weren't posted to the committers list due to moderation.
Marc has fixed it now, so I just changed the address back to post
directly to pgsql-committers.
//Magnus
>
>
>OK, that's really what I needed... messages
Log Message:
---
Change commit email addres sback to pgsql-committers now that the list has been fixed.
Modified Files:
--
CVSROOT:
loginfo (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/CVSROOT/loginfo.diff?r1=1.3&r2=1.4)
_
Log Message:
---
Persuade plpython to build on OS X.
Modified Files:
--
pgsql-server/src/pl/plpython:
Makefile (r1.13 -> r1.14)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/pl/plpython/Makefile.diff?r1=1.13&r2=1.14)
OK, that's really what I needed... messages sent to pgsql-committers
with different recipient addresses.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
--- Begin Message ---
Log Message:
---
Add mention of NetLimiter as a product with LSP-issues.
Modified Files:
--
Log Message:
---
GUC assign hooks that look at external state in deciding whether a
setting is valid must ignore that state and permit the assignment anyway
when source is PGC_S_OVERRIDE. Otherwise they may disallow a rollback
at transaction abort, which is The Wrong Thing. Per example fr
Log Message:
---
Add mention of initdb permissions errors when parent directories doesn't grant the
service user read permissions.
Modified Files:
--
web:
FAQ_windows.html (r1.5 -> r1.6)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/web/FAQ_wind
Log Message:
---
Fix slightly misleading description of PERFORM syntax.
Modified Files:
--
pgsql-server/doc/src/sgml:
plpgsql.sgml (r1.46 -> r1.47)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/doc/src/sgml/plpgsql.sgml.diff?r1=1.46&r2=1.47)
---
Log Message:
---
Add mention of NetLimiter as a product with LSP-issues.
Modified Files:
--
web:
FAQ_windows.html (r1.4 -> r1.5)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/web/FAQ_windows.html.diff?r1=1.4&r2=1.5)
__
Kris Jurka <[EMAIL PROTECTED]> writes:
> Well, it's not really truncated it just overflows long long.
Oh, okay, I finally get the point --- it's the difference between signed
and unsigned that's at issue.
I suppose that the UINT64CONST macro really ought to use x##ULL not
x##LL. Does anyone thin
On Fri, 24 Sep 2004, Tom Lane wrote:
> Kris Jurka <[EMAIL PROTECTED]> writes:
> > UINT64CONST produces these in a number of places:
> > "xlog.c", line 552: warning: constant promoted to unsigned long long
>
> > it likes either ##ULL or unadorned. The problem is we're taking a
> > constant lar
On Fri, 24 Sep 2004, Neil Conway wrote:
On Fri, 2004-09-24 at 19:10, Kris Jurka wrote:
Supposedly so we can monitor the activity of all of the projects hosted on
pgfoundry. You missed the discussion this summer, but Peter E. and myself
think it's a bad idea, Marc likes it and everyone else doesn't
Kris Jurka <[EMAIL PROTECTED]> writes:
> UINT64CONST produces these in a number of places:
> "xlog.c", line 552: warning: constant promoted to unsigned long long
> it likes either ##ULL or unadorned. The problem is we're taking a
> constant larger than long long and explicitly saying it's a long
On Fri, 24 Sep 2004, Tom Lane wrote:
> > UINT64CONST produces these in a number of places:
> > "xlog.c", line 552: warning: constant promoted to unsigned long long
>
> This is pretty annoying, considering that the entire point of the
> UINT64CONST macro is to suppress such complaints. Can you
On Fri, 2004-09-24 at 19:10, Kris Jurka wrote:
> Supposedly so we can monitor the activity of all of the projects hosted on
> pgfoundry. You missed the discussion this summer, but Peter E. and myself
> think it's a bad idea, Marc likes it and everyone else doesn't seem to
> care.
Well, let me
On Fri, 24 Sep 2004, Neil Conway wrote:
> Why does pgfoundry commit mail go to pgsql-committers in the first
> place?
>
Supposedly so we can monitor the activity of all of the projects hosted on
pgfoundry. You missed the discussion this summer, but Peter E. and myself
think it's a bad idea,
16 matches
Mail list logo
