Logical Replication - Source and Destination Table Name Not The Same

Hi, Is it possible to define logical replication where the source and destination table names are not the same. I need to sync a table from some source, but already have a table with the same name. Thanks Avi IMPORTANT - This email and any attachments is intended for the above named addressee

Re: table name

> On 11 Jun 2020, at 20:58, Paul Förster wrote: > > Hi Marc, > >> On 11. Jun, 2020, at 20:54, Marc Millas wrote: >> sorry if my question is tooo simple :-) > > it's not. :-) > >> obviously if I ask: >> select * from regions-20180101; >> I get a syntax error. >> if I try select * from $$regi

Re: table name

Hi Marc, > On 11. Jun, 2020, at 20:54, Marc Millas wrote: > sorry if my question is tooo simple :-) it's not. :-) > obviously if I ask: > select * from regions-20180101; > I get a syntax error. > if I try select * from $$regions_20180101$$; > I get another syntax error. > If I try to rename tha

Re: table name

> sorry if my question is tooo simple :-) > > > > I got a shapefile from the french gov. > > I import it with postgis 3.01 utility. > > fine ! > > the table created by this utility is named regions-20180101 > > with the dash in the middle. > > I see that table

Re: table name

e created by this utility is named regions-20180101 > with the dash in the middle. > I see that table name in pg_class, and, also, in the geometry_columns view. > > > obviously if I ask: > select * from regions-20180101; > I get a syntax error. > if I try select * from $$re

table name

sorry if my question is tooo simple :-) I got a shapefile from the french gov. I import it with postgis 3.01 utility. fine ! the table created by this utility is named regions-20180101 with the dash in the middle. I see that table name in pg_class, and, also, in the geometry_columns view

Re: table name "unnest" specified more than once

On Thursday, February 27, 2020, Guyren Howe wrote: > # select > * > from > unnest(array[array['a', 'b'], array['c', 'c']]), > unnest(array[array['1', '2'], array['3', '4']]); > ERROR: 42712:

table name "unnest" specified more than once

# select * from unnest(array[array['a', 'b'], array['c', 'c']]), unnest(array[array['1', '2'], array['3', '4']]); ERROR: 42712: table name "unnest" specified more than once I’m trying

Re: dump and restore ordered by schema or table name

Em ter, 4 de jun de 2019 às 17:16, PegoraroF10 escreveu: > Our database has 180 schemas with 100 tables each, with majority of them > being small tables. Then, when we do a dump or restore we don´t know how > much time it´ll spend to do that job. > > So, there is an option to dump or restore orde

dump and restore ordered by schema or table name

Our database has 180 schemas with 100 tables each, with majority of them being small tables. Then, when we do a dump or restore we don´t know how much time it´ll spend to do that job. So, there is an option to dump or restore ordered alphabetically ? It could be by schema or table, do we have it ?

Re: Find schema-qualified table name given unqualified name

Aron Widforss writes: > I'm interested in finding a (any) unique identifier for a table given an > unqualified name of the table. Is that feasible in SQL or a C function? Something like this might help you: select relnamespace::regnamespace from pg_class where oid = 'mytable

Find schema-qualified table name given unqualified name

Hi, I'm interested in finding a (any) unique identifier for a table given an unqualified name of the table. Is that feasible in SQL or a C function? Regards, Aron Widforss