Thread: 5 Weeks till feature freeze or (do you know where your patch is?)

Hello,

5 weeks to feature freeze folks. Please provide updates including if you
think you will have a patch submitted before feature freeze. Be
realistic, if you can't make it -- say so.


Alvaro Herrera: Autovacuum improvements (maintenance window etc..)
Gavin Sherry: Bitmap Indexes (on disk), possible basic Window functions
Greg Stark: WITH/Recursive Queries?
Andrei Kovalesvki: Some Win32 work with Magnus
Magnus Hagander: VC++ support (thank goodness)
Heikki Linnakangas: Vacuum for Bitmap Indexes, Group Index Tuples
Oleg Bartunov: Tsearch2 in core
Neil Conway: Patch Review (including enums), pg_fcache
PeterE: XML
ITAGAKI Takahiro: Dead space map, load distributed checkpoints
Stephen Frost: Default permission per object/schema
Tom Lane: Cost based functions, operator overhaul, Plan Invalidation?
Simon Riggs: HOT ( you know he just is )
Pavan Deolasee: HOT ( never met him )
Teodor Sigaev: Tsearch2 in core (with Oleg)
Jeff Davis: Synchronized scanning
Henry Hotz: GSSAPI (with Magnus)
Andrew Dunstan: Something with COPY? Andrew?
David Fetter: Arrays of compound types

Looking for updates on Updateable views. Anyone? Bueller?

Vertical projects:

Pavel Stehule: PLpsm
Alexey Klyukin: PLphp
Andrei Kovalesvki: ODBCng
Neil Conway: pgmemcache
Josh Drake: pgmemcache


This close to feature freeze it is really time for people to get
pounding on patch review!!!

Sincerely,

Joshua D. Drake





--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

Joshua D. Drake wrote:
> Andrew Dunstan: Something with COPY? Andrew?
>
>

The only thing I can think of is to remove the support for ancient COPY
syntax from psql's \copy, as suggested here:
http://archives.postgresql.org/pgsql-hackers/2007-02/msg01078.php

That's hardly a feature - more a matter of tidying up.

>
> Neil Conway: pgmemcache
> Josh Drake: pgmemcache
>


what does this refer to?


cheers

andrew

>>
>> Neil Conway: pgmemcache
>> Josh Drake: pgmemcache
>>
>
>
> what does this refer to?

Neil is cleaning up the code, I am cleaning up the docs.

Joshua D. Drake

>
>
> cheers
>
> andrew
>


--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

> The only thing I can think of is to remove the support for ancient COPY
> syntax from psql's \copy, as suggested here:
> http://archives.postgresql.org/pgsql-hackers/2007-02/msg01078.php
>
> That's hardly a feature - more a matter of tidying up.

I thought you were being sponsored for something?

Joshua D. Drake


--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

"Joshua D. Drake" <jd@commandprompt.com> writes:

> Greg Stark: WITH/Recursive Queries?

Uhm, I posted two weeks ago saying I had to shelve that temporarily.

On the other hand I've submitted a patch to reduce the storage overhead of
varlenas under 128 bytes by 3-7 bytes each.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

Gregory Stark wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>
>> Greg Stark: WITH/Recursive Queries?
>
> Uhm, I posted two weeks ago saying I had to shelve that temporarily.

I can't read every email :)

Can someone pick this up? This would be the second time that this has
been dropped. Anyone?

>
> On the other hand I've submitted a patch to reduce the storage overhead of
> varlenas under 128 bytes by 3-7 bytes each.

Cool!

Joshua D. Drake





--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

On Fri, 2007-02-23 at 13:24 -0800, Joshua D. Drake wrote:
> Jeff Davis: Synchronized scanning

I am still on target. I'm scheduling some benchmarks on real hardware
and real queries in the next week or two. If those show the results I
expect, I'll be ready before feature freeze.

Regards,
    Jeff Davis

Jeff,

> I am still on target. I'm scheduling some benchmarks on real hardware
> and real queries in the next week or two. If those show the results I
> expect, I'll be ready before feature freeze.

Send me a patch against 8.2.3 and I'll pass it to the Sun benchmarking
team.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

"Gregory Stark" <stark@enterprisedb.com> writes:

> "Joshua D. Drake" <jd@commandprompt.com> writes:
>
>> Greg Stark: WITH/Recursive Queries?
>
> Uhm, I posted two weeks ago saying I had to shelve that temporarily.
>
> On the other hand I've submitted a patch to reduce the storage overhead of
> varlenas under 128 bytes by 3-7 bytes each.

oops, that's actually 3-6 bytes.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

Joshua D. Drake wrote:

<snip>

> Magnus Hagander: VC++ support (thank goodness)

I would much appreciate more people testing and commenting on this one,
from the version in CVS head.



//Magnus

I am working on it with the target of 8.3. I am posting WIP patches
since couple of weeks. One of the objectives of publishing WIP
patches, even though they are not well tested (for correctness as
well as performance) is to get early feedback on the design and
code. It would really help if one or more of the community members
look at the code  so that we don't have last minute gotchas.

Thanks,
Pavan

--

EnterpriseDB     http://www.enterprisedb.com

On Feb 23, 2007, at 1:24 PM, Joshua D. Drake wrote:

> Henry Hotz: GSSAPI (with Magnus)

Progressing.  Had hoped to have alpha patches by March 1, but I just
got handed a proposal that I have to do by then.  I trust it's OK to
send the first version in next week?

No real issues, except I haven't disentangled the SSL buffering to
disentangle my security layer from theirs.

Question:  are there any corresponding deadlines for the Java client
code that I need to worry about?
------------------------------------------------------------------------
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu

Henry B. Hotz wrote:
>
> On Feb 23, 2007, at 1:24 PM, Joshua D. Drake wrote:
>
>> Henry Hotz: GSSAPI (with Magnus)
>
> Progressing.  Had hoped to have alpha patches by March 1, but I just got
> handed a proposal that I have to do by then.  I trust it's OK to send
> the first version in next week?

Feature freeze is the end of March so I would say yes.

>
> No real issues, except I haven't disentangled the SSL buffering to
> disentangle my security layer from theirs.
>
> Question:  are there any corresponding deadlines for the Java client
> code that I need to worry about?

You would need to talk to the jdbc folks about that I would guess. There
development cycle is independent of .Org.

Joshua D. Drake

> ------------------------------------------------------------------------
> The opinions expressed in this message are mine,
> not those of Caltech, JPL, NASA, or the US Government.
> Henry.B.Hotz@jpl.nasa.gov, or hbhotz@oxy.edu
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>


--

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

On Tue, 27 Feb 2007, Henry B. Hotz wrote:

> Question:  are there any corresponding deadlines for the Java client code
> that I need to worry about?

The JDBC driver will release a new version at the same time as the server,
but we don't have nearly as strict rules about feature freeze/beta.  We
don't need multiple months of beta so as long as the patch isn't terribly
complicated we'll accept it close to the release.

Kris Jurka