Including SQL files in extension scripts - Mailing list pgsql-hackers

From Jeremy Finzel
Subject Including SQL files in extension scripts
Date
Msg-id CAMa1XUjV0cWqpssp=Jk=qvDEfNL6RMVBu-1WqqGUkwNR7aOB+Q@mail.gmail.com
Whole thread Raw
List pgsql-hackers
In writing extension update scripts, I find it to be really difficult to grok diffs for example in changed view or function definitions when a new extension script has to include the whole definition in a new file.  I want to rather use separate files for these objects, then use something like psql's \i to include the definitions so that version control (and management of these files) becomes easier, but this does not appear to be supported.  Does anyone have any recommendations here?

Currently, I often simply opt to create a script that builds out the extension SQL files from separated sql files so that I can more easily maintain them.  But I was hoping there is a better way.  Any ideas would be much appreciated.

Thanks,
Jeremy

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
Next
From: Tom Lane
Date:
Subject: Re: Boolean partitions syntax