Auto-partitioning in COPY

Started by Leonardo Francalancialmost 16 years ago3 messagesgeneral
Jump to latest
#1Leonardo Francalanci
m_lists@yahoo.it

At this page:

http://wiki.postgresql.org/wiki/Auto-partitioning_in_COPY

I read:
"The automatic hierarchy loading code is currently integrated
in the code of the COPY command of Postgres 8.5"

Is that true?

#2Bruce Momjian
bruce@momjian.us
In reply to: Leonardo Francalanci (#1)
Re: Auto-partitioning in COPY

Leonardo F wrote:

At this page:

http://wiki.postgresql.org/wiki/Auto-partitioning_in_COPY

I read:
"The automatic hierarchy loading code is currently integrated
in the code of the COPY command of Postgres 8.5"

Is that true?

It might be true for Aster Data's version of Postgres, but not for the
community version. I have relabeled those pages as "Aster Data", and
emailed the author mentioning the problem and asking why Aster features
are being listed on our wiki, which causes confusion.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ None of us is going to be here forever. +

#3Greg Smith
gsmith@gregsmith.com
In reply to: Bruce Momjian (#2)
Re: Auto-partitioning in COPY

Bruce Momjian wrote:

Leonardo F wrote:

At this page:

http://wiki.postgresql.org/wiki/Auto-partitioning_in_COPY

I read:
"The automatic hierarchy loading code is currently integrated
in the code of the COPY command of Postgres 8.5"

Is that true?

It might be true for Aster Data's version of Postgres, but not for the
community version. I have relabeled those pages as "Aster Data", and
emailed the author mentioning the problem and asking why Aster features
are being listed on our wiki, which causes confusion.

These wiki pages described features that were submitted for community
PostgreSQL a while back:
https://commitfest.postgresql.org/action/patch_view?id=173
https://commitfest.postgresql.org/action/patch_view?id=205

But that were both returned with feedback suggesting they weren't
suitable to apply, and so far they haven't been followed up on since.
I'm going to revert your edits because they just make the situation more
confusing (those aren't patches in Aster's product!) and label them
correctly.

--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.us