<?xml version="1.0" encoding="ISO-8859-1"?>
<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
>

<channel rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/">
<title>talkaboutdatabases.com Pgsql Committers</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/</link>
<description>$</description>
<dc:language>en-us</dc:language>
<dc:rights>Copyright 2003-2005, Talk About Network. All Rights Reserved.</dc:rights>
<dc:date>2008-07-08T23:07:14+00:00</dc:date>
<dc:publisher>TAN</dc:publisher>
<dc:creator>rss@talkaboutnetwork.com</dc:creator>
<dc:subject>Discussion</dc:subject>
<syn:updatePeriod>hourly</syn:updatePeriod>
<syn:updateFrequency>1</syn:updateFrequency>
<syn:updateBase>1970-01-01T00:00+00:00</syn:updateBase>
<items>
 <rdf:Seq>
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17764.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17763.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17762.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17761.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17760.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17759.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17758.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17757.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17756.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17755.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17753.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17752.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17751.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17750.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17749.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17748.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17747.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17746.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17745.html" />
<rdf:li rdf:resource="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17744.html" />
 </rdf:Seq>
</items>
<image rdf:resource="http://tan12.talkaboutnetwork.com/images/spacer.gif" /> 
<textinput rdf:resource="http://talkaboutdatabases.com/group/pgsql.committers/search.html" />
</channel>

<image rdf:about="http://tan12.talkaboutnetwork.com/images/spacer.gif">
<title>talkaboutdatabases.com Pgsql Committers</title>
<url>http://tan12.talkaboutnetwork.com/images/spacer.gif</url>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/</link>
</image>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17764.html">
<title>npgsql - Npgsql2:  Added support to not add type casts with prep</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17764.html</link>
<description>Log Message: -----------  Added support to not add type casts with prepared statements. Previous patch only added this capability for non prepared queries. Now, types without casts have the type written as unknown so type inference is done by server ...</description>
<dc:creator>fxjr@[EMAIL PROTECTED]
 (User Fxjr)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-09T03:40:36+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17763.html">
<title>pgsql: Fix performance bug in write_syslog(): the code to prefer</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17763.html</link>
<description>Log Message: ----------- Fix performance bug in write_syslog(): the code to preferentially break the log message at newlines cost O(N^2) for very long messages with few or no newlines.  For messages in the megabyte range this became the dominant cost...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-08T22:18:18+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17762.html">
<title>pgsql: Fix performance bug in write_syslog(): the code to prefer</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17762.html</link>
<description>Log Message: ----------- Fix performance bug in write_syslog(): the code to preferentially break the log message at newlines cost O(N^2) for very long messages with few or no newlines.  For messages in the megabyte range this became the dominant cost...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-08T22:18:09+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17761.html">
<title>pgsql: Fix performance bug in write_syslog(): the code to prefer</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17761.html</link>
<description>Log Message: ----------- Fix performance bug in write_syslog(): the code to preferentially break the log message at newlines cost O(N^2) for very long messages with few or no newlines.  For messages in the megabyte range this became the dominant cost...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-08T22:18:03+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17760.html">
<title>pgsql: Fix performance bug in write_syslog(): the code to prefer</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17760.html</link>
<description>Log Message: ----------- Fix performance bug in write_syslog(): the code to preferentially break the log message at newlines cost O(N^2) for very long messages with few or no newlines.  For messages in the megabyte range this became the dominant cost...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-08T22:17:55+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17759.html">
<title>pgsql: Fix performance bug in write_syslog(): the code to prefer</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17759.html</link>
<description>Log Message: ----------- Fix performance bug in write_syslog(): the code to preferentially break the log message at newlines cost O(N^2) for very long messages with few or no newlines.  For messages in the megabyte range this became the dominant cost...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-08T22:17:47+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17758.html">
<title>pgsql: Fix performance bug in write_syslog(): the code to prefer</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17758.html</link>
<description>Log Message: ----------- Fix performance bug in write_syslog(): the code to preferentially break the log message at newlines cost O(N^2) for very long messages with few or no newlines.  For messages in the megabyte range this became the dominant cost...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-08T22:17:41+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17757.html">
<title>pgbouncer - pgbouncer: remove extra argument for SBuf callback</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17757.html</link>
<description>Log Message: ----------- remove extra argument for SBuf callback  conserves memory and conforms more with general coding style.  plus few cleanups  Modified Files: --------------     pgbouncer/include:         client.h (r1.2 - r1.3)         (http://c...</description>
<dc:creator>mkz@[EMAIL PROTECTED]
 (User Mkz)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-08T20:01:56+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17756.html">
<title>pgsql: Fix WAL file cutoff point calculation in pg_standby.</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17756.html</link>
<description>Log Message: ----------- Fix WAL file cutoff point calculation in pg_standby.  Patch by Simon Riggs, per bug report from Ferenc Felhoffer  Tags: ---- REL8_3_STABLE  Modified Files: --------------     pgsql/contrib/pg_standby:         pg_standby.c (r1...</description>
<dc:creator>heikki@[EMAIL PROTECTED]
 (Heikki Linnak...</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-08T15:12:04+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17755.html">
<title>pgsql: Fix WAL file cutoff point calculation in pg_standby.</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17755.html</link>
<description>Log Message: ----------- Fix WAL file cutoff point calculation in pg_standby.  Patch by Simon Riggs, per bug report from Ferenc Felhoffer  Modified Files: --------------     pgsql/contrib/pg_standby:         pg_standby.c (r1.12 - r1.13)         (http...</description>
<dc:creator>heikki@[EMAIL PROTECTED]
 (Heikki Linnak...</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-08T15:11:58+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17753.html">
<title>pgsql: Minor improvements to the Gin internal documentation.</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17753.html</link>
<description>Log Message: ----------- Minor improvements to the Gin internal documentation.  Modified Files: --------------     pgsql/src/backend/access/gin:         README (r1.5 - r1.6)         (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/g...</description>
<dc:creator>neilc@[EMAIL PROTECTED]
 (Neil Conway)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-08T03:25:42+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17752.html">
<title>pgsql: Add comment for deadlock_timeout:          /* This is PGC</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17752.html</link>
<description>Log Message: ----------- Add comment for deadlock_timeout:          /* This is PGC_SIGHUP so all backends have the same value. */  Modified Files: --------------     pgsql/src/backend/utils/misc:         guc.c (r1.462 - r1.463)         (http://anoncv...</description>
<dc:creator>momjian@[EMAIL PROTECTED]
 (Bruce Momjia...</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-08T02:07:30+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17751.html">
<title>pgsql: Fix estimate_num_groups() to assume that GROUP BY express</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17751.html</link>
<description>Log Message: ----------- Fix estimate_num_groups() to assume that GROUP BY expressions yielding boolean results always contribute two groups, regardless of the expression contents. This is very substantially more accurate than the regular heuristic f...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-07T20:25:40+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17750.html">
<title>pgsql: Fix estimate_num_groups() to assume that GROUP BY express</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17750.html</link>
<description>Log Message: ----------- Fix estimate_num_groups() to assume that GROUP BY expressions yielding boolean results always contribute two groups, regardless of the expression contents. This is very substantially more accurate than the regular heuristic f...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-07T20:25:31+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17749.html">
<title>pgsql: Fix estimate_num_groups() to assume that GROUP BY express</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17749.html</link>
<description>Log Message: ----------- Fix estimate_num_groups() to assume that GROUP BY expressions yielding boolean results always contribute two groups, regardless of the expression contents. This is very substantially more accurate than the regular heuristic f...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-07T20:25:23+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17748.html">
<title>pgsql: Fix estimate_num_groups() to assume that GROUP BY express</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17748.html</link>
<description>Log Message: ----------- Fix estimate_num_groups() to assume that GROUP BY expressions yielding boolean results always contribute two groups, regardless of the expression contents. This is very substantially more accurate than the regular heuristic f...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-07T20:25:14+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17747.html">
<title>pgsql: Fix estimate_num_groups() to assume that GROUP BY express</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17747.html</link>
<description>Log Message: ----------- Fix estimate_num_groups() to assume that GROUP BY expressions yielding boolean results always contribute two groups, regardless of the expression contents. This is very substantially more accurate than the regular heuristic f...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-07T20:25:06+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17746.html">
<title>pgsql: Fix estimate_num_groups() to assume that GROUP BY express</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17746.html</link>
<description>Log Message: ----------- Fix estimate_num_groups() to assume that GROUP BY expressions yielding boolean results always contribute two groups, regardless of the expression contents. This is very substantially more accurate than the regular heuristic f...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-07T20:24:56+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17745.html">
<title>pgsql: Fix AT TIME ZONE (in all three variants) so that we first</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17745.html</link>
<description>Log Message: ----------- Fix AT TIME ZONE (in all three variants) so that we first try to interpret the timezone argument as a timezone abbreviation, and only try it as a full timezone name if that fails.  The zic database has four zones (CET, EET, M...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-07T18:10:12+00:00</dc:date>
</item>

<item rdf:about="http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17744.html">
<title>pgsql: Fix AT TIME ZONE (in all three variants) so that we first</title>
<link>http://www.talkaboutdatabases.com/group/pgsql.committers/messages/17744.html</link>
<description>Log Message: ----------- Fix AT TIME ZONE (in all three variants) so that we first try to interpret the timezone argument as a timezone abbreviation, and only try it as a full timezone name if that fails.  The zic database has four zones (CET, EET, M...</description>
<dc:creator>tgl@[EMAIL PROTECTED]
 (Tom Lane)
</dc:creator>
<dc:subject>Discussion</dc:subject>
<dc:date>2008-07-07T18:10:04+00:00</dc:date>
</item>


<textinput rdf:about="http://talkaboutdatabases.com/group/pgsql.committers/search.html">
<title>Search talkaboutdatabases.com Pgsql Committers</title>
<description>Search talkaboutdatabases.com Pgsql Committers</description>
<name>q</name>
<link>http://talkaboutdatabases.com/group/pgsql.committers/search.html</link>
</textinput>

</rdf:RDF>
