| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Mark ReplicationSlotCtl as PGDLLIMPORT. |
| Date: | 2019-06-13 14:53:53 |
| Message-ID: | E1hbR6v-0000vK-3H@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Mark ReplicationSlotCtl as PGDLLIMPORT.
Also MyReplicationSlot, in branches where it wasn't already.
This was discussed in the thread that resulted in c572599c6, but
for some reason nobody pulled the trigger. Now that we have another
request for the same thing, we should just do it.
Craig Ringer
Discussion: https://postgr.es/m/CAMsr+YFTsq-86MnsNng=mPvjjh5EAbzfMK0ptJPvzyvpFARuRg@mail.gmail.com
Discussion: https://postgr.es/m/345138875.20190611151943@cybertec.at
Branch
------
REL_10_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/945ae92c8a5ef929778e2e25ebf4ee1909c54954
Modified Files
--------------
src/include/replication/slot.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-06-13 21:32:14 | pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
| Previous Message | Alvaro Herrera | 2019-06-13 14:09:43 | pgsql: Fix double-word typos |