pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Julius de Bruijn <bruijn@prisma.io>
To: pgsql-general@lists.postgresql.org
Subject: Re: How are the SELECT queries reconstructed in pg_views
Date: Tue, 28 Mar 2023 13:23:40 -0700
Message-ID: <73b0f3b2-819d-4cb3-6101-cd02c033da5e@aklaver.com> (raw)
In-Reply-To: <25b7f08f-1a5d-669a-1678-9def044df0bf@prisma.io>
References: <25b7f08f-1a5d-669a-1678-9def044df0bf@prisma.io>

On 3/28/23 06:43, Julius de Bruijn wrote:
> Hi,
> 
> We at Prisma are implementing developer tooling for PostgreSQL
> database amongst the others. One part of our tooling is the migration
> of schema changes to the database. We do that by diffing the schema
> from the file system against the one we introspect from the database;
> storing the changes to a migration file.
> 
> We are right now extending this to cover database views, and right now
> I'm looking for ways to compare the SQL written by the user against
> the SQL definition found in the pg_views view in the database.
> 
> We do have a good SQL parser, which makes minor differences such as
> whitespace or newlines not matter in the comparison. What makes things
> more difficult is how PostgreSQL reconstructs the SELECT query before
> storing it to the database, as is written in the documentation:
> 
> https://www.postgresql.org/docs/current/view-pg-views.html
> 
> I haven't been able to find exactly what changes PostgreSQL does when
> reconstructing the query, but I've successfully been able to create
> views where the resulting query differs from what I wrote. Is there
> any documentation for this feature where I can learn more about what
> happens before the query is stringified to the information schema? Or,
> even better, is there a way for me to send a query to the database and
> as a result get back a reconstructed query?


SELECT pg_catalog.pg_get_viewdef('61822'::pg_catalog.oid, true);
          pg_get_viewdef
--------------------------------
   SELECT up_test.id AS up_id,  +
      up_test.col_1 AS bool_col,+
      up_test.col_2 AS col2     +
     FROM up_test;

Find pg_get_viewdef here:
https://www.postgresql.org/docs/current/functions-info.html

Source here:

~/src/backend/utils/adt/ruleutils.c

> 
> Thank you!
> 
> Julius de Bruijn
> Software Engineer
> https://www.prisma.io/
> 
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com






view thread (3+ messages)  latest in thread

Message-ID: <73b0f3b2-819d-4cb3-6101-cd02c033da5e@aklaver.com>
Permalink:  ../73b0f3b2-819d-4cb3-6101-cd02c033da5e@aklaver.com/
Also on:    postgresql.org/message-id/73b0f3b2-819d-4cb3-6101-cd02c033da5e@aklaver.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: adrian.klaver@aklaver.com, bruijn@prisma.io
  Subject: Re: How are the SELECT queries reconstructed in pg_views
  In-Reply-To: <73b0f3b2-819d-4cb3-6101-cd02c033da5e@aklaver.com>
  References: <25b7f08f-1a5d-669a-1678-9def044df0bf@prisma.io> <73b0f3b2-819d-4cb3-6101-cd02c033da5e@aklaver.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox