Fix sequences dependencies tracking.

[dimitri]

A single sequence could be used by more than one table/column thanks to calling the nextval() function in the default value definition of the column. That said, a sequence is OWNED BY a single table.

In this patch we fix the case where the table that owns the sequence is filtered out from the pgcopydb scope while another table that uses the same sequence is to be copied over... with the sequence, then.

A simple way to create the situation is using the following DDL:

create table app.foo(id bigserial, f1 text);
create table copy.foo(like app.foo including all);

And then filter-out schema app from pgcopydb scope.

Fixes #390.

[andyatkinson]

Is there a way I can run the newer version via Docker? Looks like the current version is v0.12 #352 from June 2023 and there isn't yet a release branch for a new version I'm seeing, although I'm guessing it would be v0.13.

In local development I run Mac OS and in production we run on some Linux container (CentOS I think) so we'd be interested in whatever next version this update lands in for Linux as well.

Thanks!

[dimitri]

At the moment we don't have an automated CI recipe to build a docker image at each commit in the main branch, so instead you can build a docker image from the current source by doing make build. It expands to the following:

$ make version
$ docker build -t pgcopydb .

So you could also use that to label the image with your own tags etc if needed.