Log Message:
---
Cleanup some ancient Ultrix / Alpha code in main() that is intended to
modify how unaligned memory accesses are dealt with. Document that this
is really what is going on, and merge the NOFIXADE and NOPRINTADE code
paths.
Modified Files:
--
pgsql-server/src/
Kris Jurka <[EMAIL PROTECTED]> writes:
> char * vs unsigned char * are a good number of them, but I also see:
> "path.c", line 35: warning: storage class after type is obsolescent
Okay, that's easily fixed.
> UINT64CONST produces these in a number of places:
> "xlog.c", line 552: warning: consta
Log Message:
---
shmdt takes a void* parameter, per Kris Jurka.
Modified Files:
--
pgsql-server/src/backend/port:
sysv_shmem.c (r1.37 -> r1.38)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/port/sysv_shmem.c.diff?r1=1.37&r2=1.38)
---
On Fri, 2004-09-24 at 14:38, Marc G. Fournier wrote:
> Please change it back
Why does pgfoundry commit mail go to pgsql-committers in the first
place?
-Neil
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Log Message:
---
Fix gratuitous weirdness in function prototype, per Kris Jurka.
Modified Files:
--
pgsql-server/src/port:
path.c (r1.35 -> r1.36)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/port/path.c.diff?r1=1.35&r2=1.36)
--
Log Message:
---
Okay, I'm tired of reading gripes from OS X users ... add a regression
variant file to cover OS X 10.3's bizarre minus-zero behavior.
Added Files:
---
pgsql-server/src/test/regress/expected:
geometry_2.out (r1.1)
(http://developer.postgresql.or
On Thu, 23 Sep 2004, Tom Lane wrote:
> Kris Jurka <[EMAIL PROTECTED]> writes:
> > It passes regression tests,
>
> Regression tests on what exactly --- which platform, which compiler?
> (The gcc and non-gcc paths are different on Solaris, so if you can
> test both it'd be worth doing. Also some
Please change it back ... I just added:
post
allow
$host =~ /pgfoundry\.org/
to the committers list that should have commits pass through directly now
...
On Thu, 23 Sep 2004, User Mha wrote:
Log Message:
---
Update address for CVS messages to be [EMAIL PROTECTED] to avoid slow mail forwa
Log Message:
---
Update address for CVS messages to be [EMAIL PROTECTED] to avoid slow mail forwarding
on pgsql-committers
Modified Files:
--
CVSROOT:
loginfo (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/CVSROOT/loginfo.diff?r1=1
Log Message:
---
Updated readme.
Modified Files:
--
pginst:
README (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/README.diff?r1=1.3&r2=1.4)
---(end of broadcast)---
TIP 9: the
Log Message:
---
Add PgOleDb, & MS VC++ compatible libs. Bump version to -dev4.
Modified Files:
--
pginst:
Makefile (r1.17 -> r1.18)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/Makefile.diff?r1=1.17&r2=1.18)
Makefile.config (r1.1
Log Message:
---
Run contrib installations inside a transaction. Disable non-default installation
features (template1 was getting full of *all* contrib modules).
Modified Files:
--
pginst/ca:
pginstca.c (r1.37 -> r1.38)
(http://cvs.pgfoundry.org/cgi-bin/cv
On Fri, Sep 24, 2004 at 12:15:23PM +1000, Neil Conway wrote:
> On Fri, 2004-09-24 at 11:53, Tom Lane wrote:
> > Ideally I'd like it warning-free on everything, but I'm not sure how
> > practical that is. The main thing that non-gcc compilers tend to warn
> > about in my experience is "char *" vs "
On Fri, 2004-09-24 at 11:53, Tom Lane wrote:
> Ideally I'd like it warning-free on everything, but I'm not sure how
> practical that is. The main thing that non-gcc compilers tend to warn
> about in my experience is "char *" vs "unsigned char *", of which there
> are a lot of occurrences in and ar
Kris Jurka <[EMAIL PROTECTED]> writes:
> It passes regression tests,
Regression tests on what exactly --- which platform, which compiler?
(The gcc and non-gcc paths are different on Solaris, so if you can
test both it'd be worth doing. Also someone should verify that I
didn't break Solaris/Sparc,
Log Message:
---
Get rid of /*-inside-comment warning. My fault.
Modified Files:
--
pgsql-server/src/include/storage:
s_lock.h (r1.130 -> r1.131)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/include/storage/s_lock.h.diff?r1=1.130&r2=1.131)
On Fri, 24 Sep 2004, Tom Lane wrote:
> Log Message:
> ---
> Fix TAS assembly stuff for Solaris/386. (I'm not in a position to
> actually test this, but it couldn't be broken any worse than it was...)
>
It passes regression tests, but adds a warning:
"../../../../src/include/storage/s
Log Message:
---
ExecProcAppend() wasn't called ExecAppend() because the latter name was
formerly used in execMain. Since that is no longer the case, this patch
renames ExecProcAppend() to ExecAppend() for the sake of consistency.
Modified Files:
--
pgsql-server/src/backend
Log Message:
---
Minor improvements to the release notes.
Modified Files:
--
pgsql-server/doc/src/sgml:
release.sgml (r1.296 -> r1.297)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/doc/src/sgml/release.sgml.diff?r1=1.296&r2=1.297)
-
Log Message:
---
Fix TAS assembly stuff for Solaris/386. (I'm not in a position to
actually test this, but it couldn't be broken any worse than it was...)
Modified Files:
--
pgsql-server/src/include/storage:
s_lock.h (r1.129 -> r1.130)
(http://developer.po
Log Message:
---
Improve description of Execute message behavior, per Oliver Jowett.
Modified Files:
--
pgsql-server/doc/src/sgml:
protocol.sgml (r1.53 -> r1.54)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/doc/src/sgml/protocol.sgml.diff?r1=1.5
Log Message:
---
Fix ALTER TABLE OWNER to adjust the ownership of dependent sequences,
not only indexes. Alvaro Herrera, with some kibitzing by Tom Lane.
Modified Files:
--
pgsql-server/src/backend/commands:
tablecmds.c (r1.132 -> r1.133)
(http://developer
Log Message:
---
If we're going to print unrecognized result codes from SSL_get_error
in open_client_SSL, surely we should do it everywhere. Also make
message formatting conform to style guide.
Modified Files:
--
pgsql-server/src/interfaces/libpq:
fe-secure.c (r1.5
Log Message:
---
This patch attempts to outline the supported level of SSL within libpq.
I haven't mentioned any of
~/.postgresql/{root.crt,postgresql.crt,postresql.key} even though they
are checked for in the code, since they do not appear to be supported. I
base this on discussions in pgs
Log Message:
---
This patch logs the error code in the default case, so that the user
stands a chance of looking it up. "Unrecognised error" is always
disheartening. :-)
Dominic Mitchell
Modified Files:
--
pgsql-server/src/interfaces/libpq:
fe-secure.c (r1.49 ->
Log Message:
---
This patch attempts to note the use of the root.crt file in the server.
Given that PostgreSQL will output a message complaining about it's
absence if you're using SSL mode, I feel it's important that it gets a
mention in the documentation at some point.
Dominic Mitchell
M
26 matches
Mail list logo
