Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Epic: Support dblink and postgres_fdw extensions #3720

Open
2 of 5 tasks
vadim2404 opened this issue Mar 1, 2023 · 17 comments
Open
2 of 5 tasks

Epic: Support dblink and postgres_fdw extensions #3720

vadim2404 opened this issue Mar 1, 2023 · 17 comments
Assignees
Labels
c/compute Component: compute, excluding postgres itself f/extensions Feature: extentions t/Epic Issue type: Epic

Comments

@vadim2404
Copy link
Contributor

vadim2404 commented Mar 1, 2023

Motivation

dblink and postgres_fdw extensions are quite popular in analytical, migration, and sharding use cases. Therefore we need to install them.

DoD

As a user, I can install these two extensions and use them.

Implementation ideas

Tasks

  • Ensure that computes use JWT token while communicating with SKs and PSs
  • Add traffic metering in/out Internet #4704
  • Enable network policies that allow traffic only for selected pageserver, safekeepers, proxy, and internet traffic
  • Enable these extensions
  • Check that you cannot connect to localhost as superuser

Other related tasks and Epics

@vadim2404 vadim2404 added t/Epic Issue type: Epic c/compute Component: compute, excluding postgres itself labels Mar 1, 2023
@vadim2404 vadim2404 changed the title Epic: Support dblink and postgres_fdw extensions Epic: Support dblink, http, and postgres_fdw extensions May 16, 2023
@vmatt
Copy link

vmatt commented Nov 23, 2023

Hey, when this can be expected?

@stepashka stepashka added the f/extensions Feature: extentions label Apr 12, 2024
@ololobus ololobus changed the title Epic: Support dblink, http, and postgres_fdw extensions Epic: Support dblink and postgres_fdw extensions Sep 20, 2024
@clarkbw
Copy link

clarkbw commented Oct 8, 2024

The postgres_fdw extension is expected to release this quarter, Q4 2024

@acervantes23
Copy link

@vadim2404 what is the target ship date for this?

@vadim2404
Copy link
Contributor Author

I'll forward this question to @ololobus

@ololobus
Copy link
Member

ololobus commented Oct 14, 2024

It's currently set to the Mid-Nov here, but not sure it's gonna happen. Early Dec is more realistic. I'll keep the roadmap updated as it goes

@acervantes23
Copy link

acervantes23 commented Oct 15, 2024

can we keep GH up to date with the target ship date? my assumption is to check issues/epics for the target ship date and not spreadsheets

@ololobus
Copy link
Member

issues/epics for the target ship date and not spreadsheets

We haven't had such fields on the Epic/issue-sized tasks, only in company projects. I'm not sure that I want to create a company project for every Epic/issue-sized task. We can probably update team projects to include this dates, but then syncing everything is the mess. It's probably something to discuss with Anna and/or Bryan

@myrrc myrrc self-assigned this Nov 11, 2024
@ololobus
Copy link
Member

ololobus commented Nov 19, 2024

This week:

@ololobus
Copy link
Member

ololobus commented Nov 26, 2024

This week:

@myrrc
Copy link
Contributor

myrrc commented Dec 3, 2024

This week - still waiting for vm-runner review

@myrrc
Copy link
Contributor

myrrc commented Dec 6, 2024

Runner merged, waiting for deployment

@ololobus
Copy link
Member

ololobus commented Dec 10, 2024

This week:

  • @myrrc enable traffic metering on staging
  • @myrrc test dblink and enable

@acervantes23
Copy link

hey @ololobus will we enable this week?

@ololobus
Copy link
Member

ololobus commented Dec 13, 2024

hey @ololobus will we enable this week?

Def, not this week because it's Fri evening :) I think that we may target merging the PR next week, but cc @myrrc to correct me

@ololobus
Copy link
Member

This week:

  • @myrrc targets to merge dblink support

@ololobus
Copy link
Member

ololobus commented Dec 17, 2024

Question from @MMeent

Re: DBLink:
Do we have enough protections for that?
IIRC, we had a local:trust policy (i.e. no password), which is kinda bad when someone tries to connect to localhost with a neon_superuser dbname using e.g. dblink or postgres_fdw.

I.e. how we restrict users from connecting as cloud_admin. Heikki, exts should have a protection from that

@myrrc to double-check

Stas: if it's possible to conenct, we can probably use socket for our conns and restrict tcp localhost access

@acervantes23
Copy link

Hows this one looking @ololobus ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c/compute Component: compute, excluding postgres itself f/extensions Feature: extentions t/Epic Issue type: Epic
Projects
None yet
Development

No branches or pull requests

7 participants