tag:blogger.com,1999:blog-2356137376934964551.post3768175452054479208..comments2023-06-14T06:01:24.499-04:00Comments on Andrew Dunstan's PostgreSQL and Technical blog: Features still wantedAndrew Dunstanhttp://www.blogger.com/profile/04684286585449188201noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-2356137376934964551.post-9723327033696163182013-09-30T13:57:20.085-04:002013-09-30T13:57:20.085-04:00Andrew,
Andrew Gierth is working on Grouping Sets...Andrew,<br /><br />Andrew Gierth is working on Grouping Sets for 9.4. I'm sure he'd be happy to have help, at least code review.Josh Berkushttps://www.blogger.com/profile/09671139717468724246noreply@blogger.comtag:blogger.com,1999:blog-2356137376934964551.post-83675177647788087972013-09-30T02:47:38.307-04:002013-09-30T02:47:38.307-04:00Table partitioning. We need a real world table par...Table partitioning. We need a real world table partitioning which is not based on the assumption that the table will be split into just 10 or 12 subtables but rather in undreds or even thousands.<br />Bookkeeping and stock control, for example, require billions of lines thus asking of a partitioning schema going, for example, along with weeks over 5+ years. That's 200+ subtables.<br />Whatever implementation you choose (see the friendly manual), either you have a complex (and yet manual) and optimized partition management or a simple linear one.<br />The CHECK() predicate (just like partial non-overlapping indexes) doesn't bring you any sub-linear optimization.<br />Table partitioning is thus more an academic topic than a real world application.<br />The question should not be "how does oracle implement it" but rathger "how do we implement it.<br />Unluckily I have not enough expertise with PG source code and RDBMS programming to jump into that.<br />Anonymoushttps://www.blogger.com/profile/08159441545097076822noreply@blogger.comtag:blogger.com,1999:blog-2356137376934964551.post-73868791362475703102013-09-29T10:49:01.990-04:002013-09-29T10:49:01.990-04:00No. IIRC it was found not to be of adequate qualit...No. IIRC it was found not to be of adequate quality, and there are various other questions not yet resolved about exactly what behaviour we want to implement.Andrew Dunstanhttps://www.blogger.com/profile/04684286585449188201noreply@blogger.comtag:blogger.com,1999:blog-2356137376934964551.post-40664627131114117752013-09-29T05:05:20.487-04:002013-09-29T05:05:20.487-04:00So MERGE (https://wiki.postgresql.org/wiki/Add_MER...So MERGE (https://wiki.postgresql.org/wiki/Add_MERGE_command_GSoC_2010) has not been added to PostgreSQL?pablojhttps://www.blogger.com/profile/03043517866113096024noreply@blogger.comtag:blogger.com,1999:blog-2356137376934964551.post-80103380327212722022013-09-28T22:02:20.438-04:002013-09-28T22:02:20.438-04:00There are a few corner cases to composite types th...There are a few corner cases to composite types that make them unusable in production - especially for primary keys. To me, joining on composite typed keys is a thing of beauty when compared to joining ordinary composite field keys.<br /><br />Unfortunately, I expect there isn't enough demand composite primary keys to warrant such a feature. :( Richard Broersmahttps://www.blogger.com/profile/15248632193446037558noreply@blogger.com