Where to save data used by extension ?

From: Hao Wu <hawu(at)pivotal(dot)io>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Where to save data used by extension ?
Date: 2018-12-13 03:02:34
Message-ID: CANdi8u0FfCSLa4rkXZ9n5oO049F+6dHpR+32O=2ObMKPYs36EQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi pgsql-hackers,

I have an extension for postgresql. The extension works across some
databases, and needs to save some data. The data might be modified
dynamically by the extension, and all the changed result must be saved. I
have considered some methods.
1. Use GUC
I find no easy way to write the GUC values back to postgres.conf. And the
data might be a bit complex
2. Create a table under a special database, like postgres
The weak is the strong assumption that the database postgres does exist and
will not be dropped.
3. Create a table under a database created by the extension
A little heavy, but without dependencies.
4. Write to a native file.
The file can not sync to a standby

Currently, I use #2. Is there any better way to do this?

Thank you very much
Best Regards

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-12-13 03:22:58 Re: Making WAL receiver startup rely on GUC context for primary_conninfo and primary_slot_name
Previous Message Andreas Karlsson 2018-12-13 00:30:06 Re: Introducing SNI in TLS handshake for SSL connections