Log Message:
---
Use malloc() in GetLockConflicts() when called InHotStandby to avoid repeated
palloc calls. Current code assumed this was already true, so this is a bug fix.
Modified Files:
--
pgsql/src/backend/storage/lmgr:
lock.c (r1.191 -> r1.192)
(http
Log Message:
---
Define INADDR_NONE on Solaris when it's missing. Per a couple of buildfarm
members complaining.
Modified Files:
--
pgsql/src/include/port:
solaris.h (r1.17 -> r1.18)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/port/solaris.h
Log Message:
---
Add functions to reset the statistics counter for a single table/index or
a single function.
Modified Files:
--
pgsql/doc/src/sgml:
monitoring.sgml (r1.74 -> r1.75)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/monitoring.sgm
[email protected] (Simon Riggs) writes:
> Log Message:
> ---
> Use malloc() in GetLockConflicts() when called InHotStandby to avoid repeated
> palloc calls. Current code assumed this was already true, so this is a bug
> fix.
It seems pretty ugly to allocate the same pointer sometimes
On Thu, 2010-01-28 at 10:43 -0500, Tom Lane wrote:
> [email protected] (Simon Riggs) writes:
> > Log Message:
> > ---
> > Use malloc() in GetLockConflicts() when called InHotStandby to avoid
> > repeated
> > palloc calls. Current code assumed this was already true, so this is a bug
>
[email protected] (Magnus Hagander) writes:
> Log Message:
> ---
> Define INADDR_NONE on Solaris when it's missing. Per a couple of buildfarm
> members complaining.
This seems likely to break as much as it fixes, since there's no very
good reason to assume that whatever header should def
On Thu, Jan 28, 2010 at 16:46, Tom Lane wrote:
> [email protected] (Magnus Hagander) writes:
>> Log Message:
>> ---
>> Define INADDR_NONE on Solaris when it's missing. Per a couple of buildfarm
>> members complaining.
>
> This seems likely to break as much as it fixes, since there's no v
Magnus Hagander writes:
> On Thu, Jan 28, 2010 at 16:46, Tom Lane wrote:
>> Possibly more to the point, where are we using INADDR_NONE anyway?
> In the RADIUS code.
Oh, that's why it isn't in my tree and has zero portability track record ...
I think what this shows is we should look for a way
On Thu, Jan 28, 2010 at 17:04, Tom Lane wrote:
> Magnus Hagander writes:
>> On Thu, Jan 28, 2010 at 16:46, Tom Lane wrote:
>>> Possibly more to the point, where are we using INADDR_NONE anyway?
>
>> In the RADIUS code.
>
> Oh, that's why it isn't in my tree and has zero portability track record
Magnus Hagander writes:
> On Thu, Jan 28, 2010 at 17:04, Tom Lane wrote:
>> I think what this shows is we should look for a way to avoid using
>> INADDR_NONE.
>> From some more googling
> (http://www.opengroup.org/onlinepubs/95399/functions/inet_addr.html),
> it says it will return (in_addr_
Log Message:
---
Fix crashing bug at the end of recovery in Streaming Replication, when
restore_command is not given. Fujii Masao.
Modified Files:
--
pgsql/src/backend/access/transam:
xlog.c (r1.363 -> r1.364)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql
On Thu, Jan 28, 2010 at 17:16, Tom Lane wrote:
> Magnus Hagander writes:
>> On Thu, Jan 28, 2010 at 17:04, Tom Lane wrote:
>>> I think what this shows is we should look for a way to avoid using
>>> INADDR_NONE.
>
>>> From some more googling
>> (http://www.opengroup.org/onlinepubs/95399/funct
Magnus Hagander writes:
> On Thu, Jan 28, 2010 at 17:16, Tom Lane wrote:
>> However, now that I know the real issue is you're using inet_addr, I
>> would like to know why you're not using inet_aton instead; or even
>> better, something that also copes with IPv6.
> "Path of least resistance?"
>
On Thu, Jan 28, 2010 at 21:16, Tom Lane wrote:
> Magnus Hagander writes:
>> On Thu, Jan 28, 2010 at 17:16, Tom Lane wrote:
>>> However, now that I know the real issue is you're using inet_addr, I
>>> would like to know why you're not using inet_aton instead; or even
>>> better, something that al
Log Message:
---
Fix bug found by warning from recent gcc. patch from Tim Bunce.
Modified Files:
--
pgsql/src/pl/plperl:
plperl.c (r1.161 -> r1.162)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/plperl.c?r1=1.161&r2=1.162)
--
Sent via pgsq
Log Message:
---
Type table feature
This adds the CREATE TABLE name OF type command, per SQL standard.
Modified Files:
--
pgsql/doc/src/sgml:
information_schema.sgml (r1.44 -> r1.45)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/information_
Log Message:
---
Add new make targets "world", "install-world" and "installcheck-world" to
build, install and check just about everything.
In addition to everything built installed and tested by all, install and
installcheck targets, these build HTML Docs,
build and test contrib, and test
Log Message:
---
Fix thinko in new installcheck-world target
Modified Files:
--
pgsql:
GNUmakefile.in (r1.56 -> r1.57)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/GNUmakefile.in?r1=1.56&r2=1.57)
--
Sent via pgsql-committers mailing list (pgsql-committ
Update of /cvsroot/npgsql/Npgsql2/Tools
In directory pgfoundry.org:/tmp/cvs-serv72493/Tools
Log Message:
Directory /cvsroot/npgsql/Npgsql2/Tools added to the repository
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.p
Update of /cvsroot/npgsql/Npgsql2/Tools/FxCop
In directory pgfoundry.org:/tmp/cvs-serv84859/Tools/FxCop
Log Message:
Directory /cvsroot/npgsql/Npgsql2/Tools/FxCop added to the repository
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscrip
Update of /cvsroot/npgsql/Npgsql2/Tools/FxCop/Xml
In directory pgfoundry.org:/tmp/cvs-serv8520/Tools/FxCop/Xml
Log Message:
Directory /cvsroot/npgsql/Npgsql2/Tools/FxCop/Xml added to the repository
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to yo
Update of /cvsroot/npgsql/Npgsql2/Tools/FxCop/Repository
In directory pgfoundry.org:/tmp/cvs-serv8520/Tools/FxCop/Repository
Log Message:
Directory /cvsroot/npgsql/Npgsql2/Tools/FxCop/Repository added to the repository
--
Sent via pgsql-committers mailing list ([email protected])
Update of /cvsroot/npgsql/Npgsql2/Tools/FxCop/Engines
In directory pgfoundry.org:/tmp/cvs-serv8520/Tools/FxCop/Engines
Log Message:
Directory /cvsroot/npgsql/Npgsql2/Tools/FxCop/Engines added to the repository
--
Sent via pgsql-committers mailing list ([email protected])
To make c
Update of /cvsroot/npgsql/Npgsql2/Tools/FxCop/Rules
In directory pgfoundry.org:/tmp/cvs-serv8520/Tools/FxCop/Rules
Log Message:
Directory /cvsroot/npgsql/Npgsql2/Tools/FxCop/Rules added to the repository
--
Sent via pgsql-committers mailing list ([email protected])
To make changes
Update of /cvsroot/npgsql/Npgsql2/Tools/FxCop/Repository/Compatibility
In directory
pgfoundry.org:/tmp/cvs-serv18016/Tools/FxCop/Repository/Compatibility
Log Message:
Directory /cvsroot/npgsql/Npgsql2/Tools/FxCop/Repository/Compatibility added to
the repository
--
Sent via pgsql-committers ma
Log Message:
---
Added Tools/FxCop to Npgsql2
Added Files:
---
Npgsql2/Tools/FxCop:
CustomDictionary.xml (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/Tools/FxCop/CustomDictionary.xml?rev=1.1&content-type=text/x-cvsweb-markup)
FxC
Update of /cvsroot/npgsql/Npgsql2/Tools/Gendarme
In directory pgfoundry.org:/tmp/cvs-serv13502/Gendarme
Log Message:
Directory /cvsroot/npgsql/Npgsql2/Tools/Gendarme added to the repository
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subsc
Log Message:
---
Added Tools/Gendarme to Npgsql2
Added Files:
---
Npgsql2/Tools/Gendarme:
AUTHORS (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/Tools/Gendarme/AUTHORS?rev=1.1&content-type=text/x-cvsweb-markup)
Gendarme.Framework.dl
Log Message:
---
Fix command tag for ALTER LARGE OBJECT.
Modified Files:
--
pgsql/src/backend/tcop:
utility.c (r1.330 -> r1.331)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/utility.c?r1=1.330&r2=1.331)
--
Sent via pgsql-committers mai
29 matches
Mail list logo