On 16 October 2015 18:20:59 EEST, Bruce Momjian wrote:
>I think on-disk bitmap indexes would only beat GIN indexes in a
>read-only database on low-cardinality columns. For example, if you had
>a purchase_log table and wanted to know all the "blue" and "large"
>items
>sold at a specific store, I
On Fri, Oct 16, 2015 at 12:02:03PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > Are you suggesting I remove those links? It is kind of odd to have
> > links to patches for features we don't want, or just keep it?
>
> No, quite the contrary -- I think the links allow some other perso
On Fri, Oct 16, 2015 at 12:00:11PM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > I have spend the past few days updating our TODO list, removing
> > completed and now-unnecessary items:
> >
> > https://wiki.postgresql.org/wiki/Todo
>
> Thanks. We have "TodoDone" pages for items tha
Bruce Momjian wrote:
> Are you suggesting I remove those links? It is kind of odd to have
> links to patches for features we don't want, or just keep it?
No, quite the contrary -- I think the links allow some other person
research the issue including the history of patches and discussion, and
de
Bruce Momjian wrote:
> I have spend the past few days updating our TODO list, removing
> completed and now-unnecessary items:
>
> https://wiki.postgresql.org/wiki/Todo
Thanks. We have "TodoDone" pages for items that were done in specific
releases, but only for 8.4, 9.0 and 9.1. I guess it
On Fri, Oct 16, 2015 at 11:43:10AM -0300, Alvaro Herrera wrote:
> Bruce Momjian wrote:
>
> > Probably the most controvertial change was to move on-disk bitmap
> > indexes to the "not wanted" section, though I kept the links in case we
> > change our minds. I just can't see how they would be a win
Bruce Momjian wrote:
> Probably the most controvertial change was to move on-disk bitmap
> indexes to the "not wanted" section, though I kept the links in case we
> change our minds. I just can't see how they would be a win with GIN and
> in-memory bitmaps.
Yeah, I recall we discussed bitmap ind
On Fri, Oct 16, 2015 at 02:50:04PM +0530, Amit Kapila wrote:
> On Fri, Oct 16, 2015 at 8:34 AM, Bruce Momjian wrote:
>
> I have spend the past few days updating our TODO list, removing
> completed and now-unnecessary items:
>
> https://wiki.postgresql.org/wiki/Todo
>
>
>
>
On Fri, Oct 16, 2015 at 8:34 AM, Bruce Momjian wrote:
> I have spend the past few days updating our TODO list, removing
> completed and now-unnecessary items:
>
> https://wiki.postgresql.org/wiki/Todo
>
>
Thanks. It can help encourage many new entrants to community.
With Regards,
Amit
2010/3/27 Tom Lane :
> Robert Haas writes:
>> In reading through the TODO list, I noticed a few things that I think
>> are done, may be done, or may be partially done. See below.
>> Thoughts? ...Robert
>
>> Implement full support for window framing clauses.
>> - Not sure if we made any progress
Robert Haas wrote:
> In reading through the TODO list, I noticed a few things that I think
> are done, may be done, or may be partially done. See below.
> Thoughts? ...Robert
>
> Add missing operators for geometric data types
> - this is at least partly done. not sure if it is entirely done.
>
Tom Lane wrote:
> Robert Haas writes:
> > In reading through the TODO list, I noticed a few things that I think
> > are done, may be done, or may be partially done. See below.
> > Thoughts? ...Robert
>
> > Add missing operators for geometric data types
> > - this is at least partly done. not s
Robert Haas writes:
> As far as I know, exclusion constraints would work with hash opclasses
> also.
Yeah, they do.
> Do you think there's an advantage to having something that is
> hash-specific a la the btree-specific stuff we already have?
Sure: it'll be more efficient because of not needing
On Fri, Mar 26, 2010 at 12:57 PM, Tom Lane wrote:
> Robert Haas writes:
>> In reading through the TODO list, I noticed a few things that I think
>> are done, may be done, or may be partially done. See below.
>> Thoughts? ...Robert
>
>> Add missing operators for geometric data types
>> - this is
Robert Haas writes:
> In reading through the TODO list, I noticed a few things that I think
> are done, may be done, or may be partially done. See below.
> Thoughts? ...Robert
> Add missing operators for geometric data types
> - this is at least partly done. not sure if it is entirely done.
I
Thanks. TODO updated.
>
> * Disallow LOCK on view
> change to
> * -Disallow LOCK on view (Mark H)
> well, at least when my patch is applied :)
>
>
> * Allow SQL function indexes
> This seems to work in the CVS code, or I have misunderstood:
> CREATE TABLE t ( a int);
>
16 matches
Mail list logo
