Correction: the trigger on the remote table isn't going to work. I was trying
so many different things today that I confused myself. Sorry...
On the bright side the remote sequence works great and I can insert records
from the my database to the remote database now which is a step forward.
I
Thanks Tom,
Your reply helped point me in the right direction. With a little trial and
error I came up with a hack to solve my issue.
First off, I create a shared sequence for the user_id with a technique
described here:
[
https://paquier.xyz/postgresql-2/global-sequences-with-postgres_fdw
Hello,
I have a few questions inserting data using Foreign Data Wrappers (FDW).
Consider this simple example.
On PostgreSQL Database A (remote):
CREATE TABLE APP.TEST (
ID BIGSERIAL NOT NULL,
FIRST_NAME text,
LAST_NAME text,
STATUS integer NOT NULL DEFAULT 1,
CONSTRAINT
day, May 31, 2023 10:07am
To: "peter.boris...@kartographia.com"
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Hash Index on Partitioned Table
"peter.boris...@kartographia.com" writes:
> I have a rather large database with ~250 billion records in a partitioned
Dear PostgreSQL Community,
I have a rather large database with ~250 billion records in a partitioned
table. The database has been running and ingesting data continuously for about
3 years.
I had a "regular" BTree index on one of the fields (a unique bigint column) but
it was getting too big
