Excerpts from Tom Lane's message of vie nov 18 00:39:42 -0300 2011:
> Do missed autoheader run for previous commit.
Hmm, does the win32 file need updating too?
--
Álvaro Herrera
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Alvaro Herrera writes:
> Excerpts from Tom Lane's message of vie nov 18 00:39:42 -0300 2011:
>> Do missed autoheader run for previous commit.
> Hmm, does the win32 file need updating too?
I don't see HAVE_SCANDIR in there, do you?
regards, tom lane
--
Sent via pgsql-co
Excerpts from Tom Lane's message of vie nov 18 11:12:32 -0300 2011:
>
> Alvaro Herrera writes:
> > Excerpts from Tom Lane's message of vie nov 18 00:39:42 -0300 2011:
> >> Do missed autoheader run for previous commit.
>
> > Hmm, does the win32 file need updating too?
>
> I don't see HAVE_SCAND
Avoid marking buffer dirty when VACUUM has no work to do.
When wal_level = 'hot_standby' we touched the last page of the
relation during a VACUUM, even if nothing else had happened.
That would alter the LSN of the last block and set the mtime
of the relation file unnecessarily. Noted by Thom Brown.
Simon Riggs writes:
> Avoid marking buffer dirty when VACUUM has no work to do.
> When wal_level = 'hot_standby' we touched the last page of the
> relation during a VACUUM, even if nothing else had happened.
> That would alter the LSN of the last block and set the mtime
> of the relation file unne
Further review of range-types patch.
Lots of documentation cleanup today, and still more type_sanity tests.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/a1a233af66ed14d225ac2d5e7948a5cc8ed2cde6
Modified Files
--
doc/src/sgml/catalogs.sgml
Log Message:
---
Fix: [#1010992] System.Double to DOUBLE PRECISION conversion bug. Thanks Udo
Liess for excellent report, test case and fix.
Modified Files:
--
Npgsql2/src/Npgsql:
NpgsqlConnector.cs (r1.35 -> r1.36)
(http://cvs.pgfoundry.org/cgi-bin/cvswe
Log Message:
---
Fixed problem with file encoding.
Modified Files:
--
Npgsql2/testsuite/noninteractive/NUnit20:
CommandTests.cs (r1.44 -> r1.45)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/testsuite/noninteractive/NUnit20/CommandTests.cs?r1
Log Message:
---
Removed erroneous line added by mistake.
Fixed warning with NpgsqlParameters.Add method. Used AddWithValue.
Modified Files:
--
Npgsql2/testsuite/noninteractive/NUnit20:
CommandTests.cs (r1.45 -> r1.46)
(http://cvs.pgfoundry.org/cgi-bin/cvs
Avoid floating-point underflow while tracking buffer allocation rate.
When the system is idle for awhile after activity, the "smoothed_alloc"
state variable in BgBufferSync converges slowly to zero. With standard
IEEE float arithmetic this results in several iterations with denormalized
values, w
Avoid floating-point underflow while tracking buffer allocation rate.
When the system is idle for awhile after activity, the "smoothed_alloc"
state variable in BgBufferSync converges slowly to zero. With standard
IEEE float arithmetic this results in several iterations with denormalized
values, w
Avoid floating-point underflow while tracking buffer allocation rate.
When the system is idle for awhile after activity, the "smoothed_alloc"
state variable in BgBufferSync converges slowly to zero. With standard
IEEE float arithmetic this results in several iterations with denormalized
values, w
Avoid floating-point underflow while tracking buffer allocation rate.
When the system is idle for awhile after activity, the "smoothed_alloc"
state variable in BgBufferSync converges slowly to zero. With standard
IEEE float arithmetic this results in several iterations with denormalized
values, w
Avoid floating-point underflow while tracking buffer allocation rate.
When the system is idle for awhile after activity, the "smoothed_alloc"
state variable in BgBufferSync converges slowly to zero. With standard
IEEE float arithmetic this results in several iterations with denormalized
values, w
14 matches
Mail list logo