Re: [17] CREATE SUBSCRIPTION ... SERVER

Joe Conway <mail@joeconway.com>

From: Joe Conway <mail@joeconway.com>
To: Jeff Davis <pgsql@j-davis.com>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2023-08-31T21:17:29Z
Lists: pgsql-hackers
On 8/31/23 12:52, Jeff Davis wrote:
> On Thu, 2023-08-31 at 10:59 +0530, Ashutosh Bapat wrote:
>> The server's FDW has to be postgres_fdw. So we have to handle the
>> awkward dependency between core and postgres_fdw (an extension).
> 
> That sounds more than just "awkward". I can't think of any precedent
> for that and it seems to violate the idea of an "extension" entirely.
> 
> Can you explain more concretely how we might resolve that?


Maybe move postgres_fdw to be a first class built in feature instead of 
an extension?

-- 
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com




Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Document new catalog columns, missed in commit 8185bb5347.

  2. Refactor to remove ForeignServerName().

  3. GetSubscription(): use per-object memory context.

  4. Fix dependency on FDW's connection function.

  5. ALTER SUBSCRIPTION ... SERVER test.

  6. Fix pg_dump for CREATE FOREIGN DATA WRAPPER ... CONNECTION.

  7. Clean up postgres_fdw/t/010_subscription.pl.

  8. CREATE SUBSCRIPTION ... SERVER.

  9. Allow upgrades to preserve the full subscription's state.