Log Message:
---
Add FAQ item about how patches are reviewed.
Modified Files:
--
pgsql/doc:
FAQ_DEV (r1.131 -> r1.132)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ_DEV.diff?r1=1.131&r2=1.132)
pgsql/doc/src/FAQ:
FAQ_DEV.html (r1.135
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > This has been saved for the 8.4 release:
> > http://momjian.postgresql.org/cgi-bin/pgpatches_hold
>
> Too late ;-)
Too late, already removed. ;-)
--
Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us
EnterpriseD
Bruce Momjian <[EMAIL PROTECTED]> writes:
> This has been saved for the 8.4 release:
> http://momjian.postgresql.org/cgi-bin/pgpatches_hold
Too late ;-)
regards, tom lane
---(end of broadcast)---
TIP 9: In versions bel
This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Gregory Stark wrote:
>
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>
> > Magnus Hagander <[EMAIL PROTECTED]> writes:
>
Log Message:
---
Implement rdbmsRelTable
Modified Files:
--
pgsnmpd:
Makefile (r1.13 -> r1.14)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/Makefile.diff?r1=1.13&r2=1.14)
TODO.txt (r1.7 -> r1.8)
(http://cvs.pgfoundry.org/cgi
Log Message:
---
Done:
> * -Allow ORDER BY ... LIMIT # to select high/low value without sort or
<
< Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
< all values to return the high/low value. Instead The idea is to do a
< sequential scan to find the high/low va
Update of /cvsroot/pgsnmpd/pgsnmpd/RDBMS-MIB_src/rdbmsRelTable
In directory pgfoundry.org:/tmp/cvs-serv21414/rdbmsRelTable
Log Message:
Directory /cvsroot/pgsnmpd/pgsnmpd/RDBMS-MIB_src/rdbmsRelTable added to the
repository
---(end of broadcast)---
Log Message:
---
Implement rdbmsSrvInfoHighwaterInboundAssociations
Update TODO list
Remove .o files erroneously added to the repository
Modified Files:
--
pgsnmpd:
TODO.txt (r1.6 -> r1.7)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgsnmpd/pgsnmpd/TODO.tx
Log Message:
---
Add a line to the EXPLAIN ANALYZE output for a Sort node, showing the
actual sort strategy and amount of space used. By popular demand.
Modified Files:
--
pgsql/src/backend/commands:
explain.c (r1.162 -> r1.163)
(http://developer.postgresq
On Fri, May 04, 2007 at 12:38:18PM -0400, Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > Could we show it in EXPLAIN ANALYZE somehow? I'm thinking it would be good
> > to see at runtime (for example as a hint that if you put in a bit more
> > work_mem it might get used)
>
> I do
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
>> Could we show it in EXPLAIN ANALYZE somehow? I'm thinking it would be good
>> to see at runtime (for example as a hint that if you put in a bit more
>> work_mem it might get used)
>
> I don't see that this is
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Could we show it in EXPLAIN ANALYZE somehow? I'm thinking it would be good
> to see at runtime (for example as a hint that if you put in a bit more
> work_mem it might get used)
I don't see that this is any more interesting than whether the sort
spille
On Fri, May 04, 2007 at 10:04:08AM -0400, Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > Is there some way to see in the generated query plan if this optimisation
> > is used?
>
> If there's a SORT just below a LIMIT (that has a limit, ie it's not just
> an OFFSET), then it's po
Log Message:
---
Updated Russian translation from Andrey Repko
Modified Files:
--
pginst/lang:
ru.xml (r1.20 -> r1.21)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/lang/ru.xml.diff?r1=1.20&r2=1.21)
---(end of broa
User Petere wrote:
> Log Message:
> ---
> Put Autotools-generated files into subdirectory config/; add macro files
> used from PostgreSQL there so you don't need a PostgreSQL source tree to
> bootstrap the code.
>
> Added Files:
> ---
> psqlodbc/config:
> general.m4
Log Message:
---
tas() support for Renesas' M32R processor. Kazuhiro Inaoka
Modified Files:
--
pgsql:
configure (r1.546 -> r1.547)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.diff?r1=1.546&r2=1.547)
configure.in (r1.513 -> r1.514)
Log Message:
---
Make clearer how arguments and return values in pl/perl are escaped. This is to
clarify the situation that Theo Schlossnagle recently reported on -bugs.
Modified Files:
--
pgsql/doc/src/sgml:
plperl.sgml (r2.65 -> r2.66)
(http://developer.
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Do we want to add other compiler specific fixes, such as the MSVC one?
Didn't see much point; the exit() call is useless but shouldn't add much
code bloat. The only reason I bothered to special-case gcc is that so
many of us use it.
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Is there some way to see in the generated query plan if this optimisation
> is used?
If there's a SORT just below a LIMIT (that has a limit, ie it's not just
an OFFSET), then it's potentially used. Whether it's actually used
depends on actual row coun
Log Message:
---
Fixed HANDLE_ENLIST_IN_DTC.
(*nix compile error)
Modified Files:
--
psqlodbc:
options.c (r1.70 -> r1.71)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/options.c.diff?r1=1.70&r2=1.71)
---(end of broa
Log Message:
---
Clean up some of the accumulated Autoconf mess here. Put back the
PGAC_ARG_ macros so that the options parsing is more robust, put the
macro calls in the right order, and make the detection of the driver
manager behave less oddly. All the required macros are now in-tree,
Log Message:
---
Put Autotools-generated files into subdirectory config/; add macro files
used from PostgreSQL there so you don't need a PostgreSQL source tree to
bootstrap the code.
Modified Files:
--
psqlodbc:
Makefile.am (r1.43 -> r1.44)
(http://cvs.pgfo
Update of /cvsroot/psqlodbc/psqlodbc/config
In directory pgfoundry.org:/tmp/cvs-serv13641/config
Log Message:
Directory /cvsroot/psqlodbc/psqlodbc/config added to the repository
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, ple
Log Message:
---
Revert pg_config breakage
Modified Files:
--
psqlodbc:
configure.ac (r1.66 -> r1.67)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/configure.ac.diff?r1=1.66&r2=1.67)
---(end of broadcast)---
Log Message:
---
Russian translation update from ?? ?
Modified Files:
--
wizard/i18n/ru_RU:
StackBuilder.mo (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackbuilder/wizard/i18n/ru_RU/StackBuilder.mo.diff?r1=1.1&r2=1.2)
StackB
Log Message:
---
Russian translation from ?? ?
Added Files:
---
wizard/i18n/ru_RU:
StackBuilder.mo (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackbuilder/wizard/i18n/ru_RU/StackBuilder.mo?rev=1.1&content-type=text/x-cvsweb-markup)
Stac
Update of /cvsroot/stackbuilder/wizard/i18n/ru_RU
In directory pgfoundry.org:/tmp/cvs-serv58705/ru_RU
Log Message:
Directory /cvsroot/stackbuilder/wizard/i18n/ru_RU added to the repository
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmas
Do we want to add other compiler specific fixes, such as the MSVC one?
Should be easy enough to do if we want to...
//Magnus
On Thu, May 03, 2007 at 11:01:02PM -0300, Tom Lane wrote:
> Log Message:
> ---
> A few fixups in error handling: mark pg_re_throw() as noreturn for gcc,
> and for o
Is there some way to see in the generated query plan if this optimisation
is used?
//Magnus
On Thu, May 03, 2007 at 10:13:45PM -0300, Tom Lane wrote:
> Log Message:
> ---
> Teach tuplesort.c about "top N" sorting, in which only the first N tuples
> need be returned. We keep a heap of th
29 matches
Mail list logo
