3 ms·

Out of curiosity, how has it been working with the pganalyze team? It seems like Supabase has been able to collaborate really effectively with other teams in th

Out of curiosity, how has it been working with the pganalyze team? It seems like Supabase has been able to collaborate really effectively with other teams in the Postgres space (including pgAdmin and pgmigra, for the `diff` migrations tooling), and it's wonderful to see!

kiwicopple 3y ago
actually I forgot to mention this one to Lukas in all the chaos leading up to our Launch Week. I will do it now we talked in the past about using their library to extend some of Dan Lynch's work (https://github.com/pyramation/postgres-ast-deparser https://github.com/pyramation/postgres-ast-deparser) to create a sort of "postgres package registry" with dynamic DDL introspection. No progress on that one yet, but I'm hopeful that we'll find the bandwidth for it one day.
peferron 3y ago
> It seems like Supabase has been able to collaborate really effectively with other teams in the Postgres space (including pgAdmin and pgmigra, for the `diff` migrations tooling) I'm thankful to Supabase for their efforts, but I'm not sure I'd pick pgAdmin and migra as examples of "really effective" collaboration with other teams: as far as I know, pgAdmin's CLI feature wasn't merged upstream and sits in an outdated Supabase fork of pgAdmin which doesn't fully support Postgres 15, and migra (which has been abandoned for a while) was just used as-is.
- kiwicopple 3y ago
  fwiw, pgadmin was not for a lack of trying: https://redmine.postgresql.org/issues/6304 https://redmine.postgresql.org/issues/6304. I won't have many details about migra form the CLI team until they come online, but no doubt we'll pick up the migra support if it has been abandoned. (but I agree with the sentiment: we can always find ways to be more collaborative)
  - peferron 3y ago
    Thank you for sharing that! It's unfortunate that the pgAdmin devs weren't interested, although I understand them wanting to keep it focused on being a GUI.
    - kiwicopple 3y ago
      I agree. We've been on the other side of pull requests like this and I know how hard it can be to say "no, we need to stay focused". I appreciate their clear comms

kiwicopple 3y ago

actually I forgot to mention this one to Lukas in all the chaos leading up to our Launch Week. I will do it now we talked in the past about using their library to extend some of Dan Lynch's work (https://github.com/pyramation/postgres-ast-deparser https://github.com/pyramation/postgres-ast-deparser) to create a sort of "postgres package registry" with dynamic DDL introspection. No progress on that one yet, but I'm hopeful that we'll find the bandwidth for it one day.

peferron 3y ago

> It seems like Supabase has been able to collaborate really effectively with other teams in the Postgres space (including pgAdmin and pgmigra, for the `diff` migrations tooling) I'm thankful to Supabase for their efforts, but I'm not sure I'd pick pgAdmin and migra as examples of "really effective" collaboration with other teams: as far as I know, pgAdmin's CLI feature wasn't merged upstream and sits in an outdated Supabase fork of pgAdmin which doesn't fully support Postgres 15, and migra (which has been abandoned for a while) was just used as-is.

kiwicopple 3y ago
fwiw, pgadmin was not for a lack of trying: https://redmine.postgresql.org/issues/6304 https://redmine.postgresql.org/issues/6304. I won't have many details about migra form the CLI team until they come online, but no doubt we'll pick up the migra support if it has been abandoned. (but I agree with the sentiment: we can always find ways to be more collaborative)
- peferron 3y ago
  Thank you for sharing that! It's unfortunate that the pgAdmin devs weren't interested, although I understand them wanting to keep it focused on being a GUI.
  - kiwicopple 3y ago
    I agree. We've been on the other side of pull requests like this and I know how hard it can be to say "no, we need to stay focused". I appreciate their clear comms