Tom,
Seems a bit pointless unless we have a better example to offer instead.
intarray maybe. Or just document which logic is wrong so people don't
copy that. We owe it to people to warn them.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
--
Sent via pgsql-hackers mailing list
If we are to make the proposed schedule for 8.4 (ie, wrap RC1 tomorrow)
we've got to get pretty hard-nosed about closing out the open items at
http://wiki.postgresql.org/wiki/PostgreSQL_8.4_Open_Items
The current list is:
* do we need to worry about re-encoding file path names?
There is perhaps
Tom Lane wrote:
If we are to make the proposed schedule for 8.4 (ie, wrap RC1 tomorrow)
we've got to get pretty hard-nosed about closing out the open items at
http://wiki.postgresql.org/wiki/PostgreSQL_8.4_Open_Items
The current list is:
* do we need to worry about re-encoding file path
Magnus Hagander mag...@hagander.net writes:
Tom Lane wrote:
* do we need to worry about re-encoding file path names?
Is there really something new here for 8.4? Haven't we lived with this
same thing previously?
Right, it's a pre-existing issue --- any misbehavior in this area goes
back to
On 6/10/09 10:40 AM, Tom Lane wrote:
* contrib/seg and contrib/cube GiST index support have performance issues
Wasn't there an issue that fixing this requires a data format change?
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
--
Sent via pgsql-hackers mailing list
Josh Berkus j...@agliodbs.com writes:
On 6/10/09 10:40 AM, Tom Lane wrote:
* contrib/seg and contrib/cube GiST index support have performance issues
Wasn't there an issue that fixing this requires a data format change?
Well, that means it probably doesn't get fixed till 8.5. I'm annoyed
at
Tom,
Alternatively, we can postpone 8.4 till Oleg and Teodor have some spare
cycles to look at the patch, but who knows when that will be.
Not soon. So, +1 to go ahead.
If this issue has existed for several versions, and we're not getting a
lot of complaints, it says that either not many
Josh Berkus j...@agliodbs.com writes:
If this issue has existed for several versions, and we're not getting a
lot of complaints, it says that either not many people are using cube
and seg or they don't notice performance issues.
Mind you, if performance is terrible, then not many people
Tom,
I suspect there aren't many. What I'm more concerned about is that
people may have copied the bogus logic for use in their own datatypes.
(Which is exactly how Matthew Wakeling came to find out the problem.)
But in any case, this train is leaving the station.
Can we put a warning in the
Josh Berkus j...@agliodbs.com writes:
Tom,
I suspect there aren't many. What I'm more concerned about is that
people may have copied the bogus logic for use in their own datatypes.
(Which is exactly how Matthew Wakeling came to find out the problem.)
But in any case, this train is leaving
On Wed, 10 Jun 2009, Tom Lane wrote:
There are also a number of documentation issues open, particularly
Dimitri's work on documenting the GIST API better, but we can work
on those later. We've never considered that the RC freeze applies
to documentation.
I had a question in this area
Greg Smith gsm...@gregsmith.com writes:
On Wed, 10 Jun 2009, Tom Lane wrote:
There are also a number of documentation issues open, particularly
Dimitri's work on documenting the GIST API better, but we can work
on those later. We've never considered that the RC freeze applies
to
12 matches
Mail list logo
