On 5/15/17 02:48, Roel Janssen wrote:
> Ah yes, I see the point. The problem here is that when new features are
> added to PostgreSQL, and you rely upon them in your database schemas,
> downgrading will most likely cause loss of information.
>
> Maybe we need a wrapper script that also makes a du
Jan Nieuwenhuizen writes:
> Roel Janssen writes:
>
>> So, it would be something like:
>> postgres pg_upgrade \
>> ...
>
> It's great to have a recipe `that works', so thanks!
>
> However, whether or not we automate this, I cannot help to wonder if
> we should support downgrading -- at least to th
Jan Nieuwenhuizen writes:
> Roel Janssen writes:
>
>> So, it would be something like:
>> postgres pg_upgrade \
>> ...
>
> It's great to have a recipe `that works', so thanks!
>
> However, whether or not we automate this, I cannot help to wonder if
> we should support downgrading -- at least to the
Roel Janssen writes:
> So, it would be something like:
> postgres pg_upgrade \
> ...
It's great to have a recipe `that works', so thanks!
However, whether or not we automate this, I cannot help to wonder if
we should support downgrading -- at least to the previous version
in this case?
If I'm n
