Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Oh, wait, that's just a -patches entry; it doesn't look like Neil
> >> ever committed it. Neil, how come?
>
> > I thought this was Neil's commit that you just did:
>
> No, the one I just put in was the one you h
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Oh, wait, that's just a -patches entry; it doesn't look like Neil
>> ever committed it. Neil, how come?
> I thought this was Neil's commit that you just did:
No, the one I just put in was the one you have listed under "Avoid
needless
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Actually ... isn't this done already?
> >> http://archives.postgresql.org/pgsql-patches/2008-02/msg00176.php
>
> > Yea, removed because I thought you just did it.
>
> Oh, wait, that's just a -patches entry; it do
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Actually ... isn't this done already?
>> http://archives.postgresql.org/pgsql-patches/2008-02/msg00176.php
> Yea, removed because I thought you just did it.
Oh, wait, that's just a -patches entry; it doesn't look like Neil
ever commit
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Added to TODO:
> > * Avoid tuple some tuple copying in sort routines
> > http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php
>
> Actually ... isn't this done already?
>
> http://archives.postgresql.org/pgsql-patches/2
Added to TODO:
* Sort large UPDATE/DELETEs so it is done in heap order
http://archives.postgresql.org/pgsql-hackers/2008-01/msg01119.php
---
Tom Lane wrote:
> We've had a couple of discussions recently revolving around
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Added to TODO:
> * Avoid tuple some tuple copying in sort routines
> http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php
Actually ... isn't this done already?
http://archives.postgresql.org/pgsql-patches/2008-02/msg00176.php
"Mihai Criveti" <[EMAIL PROTECTED]> writes:
> I am trying to build PostgreSQL 8.3.1 on OpenVMS 8.3 Alpha, patched to
> UPDATE v6.0 ECO:
> $ gcc --version
> GNV Dec 10 2007 16:40:09
> HP C V7.3-009 on OpenVMS Alpha V8.3
Hmmm ... any chance of using a real gcc, instead of HP's compiler doing
a poor
With no concrete patch or performance numbers, this thread has been
removed from the patches queue.
---
Simon Riggs wrote:
>
> In heapgetpage() we hold the buffer locked while we look for visible
> tuples. That works well i
Added to TODO:
o Allow pre/data/post files when dumping a single object, for
performance reasons
http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php
---
Simon Riggs wrote:
> pg_du
Added to TODO:
* Improve WAL concurrency by increasing lock granularity
http://archives.postgresql.org/pgsql-hackers/2008-02/msg00556.php
---
Simon Riggs wrote:
>
> Paul van den Bogaard (Sun) suggested to me that we co
Added to TODO:
* Avoid tuple some tuple copying in sort routines
http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php
---
Tom Lane wrote:
> Neil Conway <[EMAIL PROTECTED]> writes:
> > I notice that several
I am trying to build PostgreSQL 8.3.1 on OpenVMS 8.3 Alpha, patched to
UPDATE v6.0 ECO:
DEC AXPVMS VMS83A_UPDATE V6.0Patch Install Val 14-MAR-2008
Using the HP C compilers:
HP C Version 7.3 for OpenVMS Alpha Systems
HP C++ Version V7.3 for OpenVMS Alpha Systems
And the GNU (GNV)
On Thu, 2008-03-20 at 21:34 +, Sam Mason wrote:
> On Thu, Mar 20, 2008 at 05:17:22PM +, Simon Riggs wrote:
> > Currently, our sort algorithm assumes that its input is unsorted. So if
> > your data is sorted on (a) and you would like it to be sorted on (a,b)
> > then we need to perform the f
On Thu, 2008-03-20 at 22:35 +, Gregory Stark wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
>
> > If we assume we use heap sort, then if we *know* that the data is
> > presorted on (a) then we should be able to emit tuples directly that the
> > value of (a) changes and keep emitting them u
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 21 Mar 2008 12:55:26 -0400
Tom Lane <[EMAIL PROTECTED]> wrote:
regression=# create table foo (f1 serial[11]);
NOTICE: CREATE TABLE will create implicit sequence "foo_f1_seq" for
serial column "foo.f1" CREATE TABLE
re
16 matches
Mail list logo