Conversation

I used to think foreign data wrappers were cool in PostgreSQL. Today I think they’re a pain in the ass.

Aug 12, 2020

Replying to

For migrations and loading external data they look like a nice tool. As part of an application distributed over multiple databases …. not so sure. What happened?

Replying to

Yep that’s it! I’ve got an application that’s distributed over quite a few different databases. PITA. Lol.

Replying to

and

Do you think that it's okay up to a certain point? Is the issue that it's cumbersome to have lots of foreign servers, or something else?

9:18 PM · Aug 12, 2020Twitter Web App

Replying to

and

I think that if all those databases are within one company, they should form one single database to form a single point of truth.

Replying to

and

I agree but here we are. They have a lot of schemas in each database with the same name and they don’t want to mess with dealing with that so putting things in one database was off the table almost immediately.

Replying to

and

If it were one or two databases I do think it would’ve been fine but when you’re running behind on deadlines and $, and then need to install extensions, create the foreign servers, AND create user mappings, that’s a lot. For a pure Postgres DBA who’s been doing it that way 1/

Replying to

and

Maybe it’s okay. It’s not okay for a team coming off of Oracle. They’re used to having a simpler way. Do they have bigger problems? Yes. Should they be doing things a completely different way? Yes. Are they going to take the ideal route? No.

Show replies