| From: | dolan(at)directdemocracysolutions(dot)com |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | FK from logged to unlogged table? |
| Date: | 2025-11-22 00:08:15 |
| Message-ID: | 5031a50c-aca7-4512-9478-95583606b5ff@Spark |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello,
I'm looking to improve bulk write performance on a table of about 23 million rows by setting it unlogged. If lost, the table can be re-generated from archived raw data. The unlogged table would be referenced from a different, logged, table by a sparse but very important foreign key.
If the unlogged table is lost, I can repair the foreign key data by re-uploading the raw data and following a different unique key. However, this would be annoying and I would rather not have to implement it if I can protect the keyed records instead.
1. Is it allowed to key from a logged table to an unlogged table?
2. What is the system behavior if the unlogged table is lost?
3. Is there a clean way to protect only the subset of records that are keyed? (Yes, I am considering periodic backups to an archive table, but there would still be some repair needed that way).
Thanks! Nice to meet you all.
-Dolan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2025-11-22 00:09:01 | Unexpected date conversion results |
| Previous Message | Hu Bert | 2025-11-21 05:54:14 | Re: postgresql-17 on debian bookworm - directories missing |