I've encountered a bug, what should I do?

Create an issue and describe your problem. Here's what we expect to see:

• A short description;
• PostgreSQL + pg_pathman's versions;
• Reproduction steps (i.e. partitioning scheme, set of executed commands, settings);

Is pg_pathman free?

Yes. It's open source, and it's published under the PostgreSQL license.

How do I view all partitions?

/* execute me! */
select * from pathman_partition_list;

How do I get pg_pathman's version?

select get_pathman_lib_version();

Does COPY FROM/TO work?

Yes. We redirect input of COPY FROM to corresponding partitions. COPY TO returns all rows.

Will pg_pathman work with N partitions?

It depends. We've tested a table with 100K+ partitions, and it works fine, since we have several caches (dispatch cache, bounds cache and some others).

I can't build pg_pathman on Ubuntu / Fedora etc. There are missing dependencies (e.g. libkrb5-dev).

See this and this.

Can I specify custom names for partitions?

Yes, you can do it by setting your custom callback. Callback is a function which would fire every time a new partition is created. Check out this article for more information and examples.

Should I use the master branch?

That depends on the result you want to achieve. If you'd like to have a stable release, please visit our releases page and pick the latest one. If you've just encountered a bug, you could try a fresh install of master branch and tell us if the problem is fixed already (and we should be rolling out a new release) or we should try harder.

Is multilevel (cascade) partitioning supported?

Unfortunately, no.

Are you going to provide a migration utility?

Yes, there's a raw prototype here, but it's not ready yet.