Re: documentation issue - extensions - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: documentation issue - extensions
Date
Msg-id CAFj8pRAuNXBepMDguNDE6OJ10XEHhpXVhGEd+SFhMCny6SdnQg@mail.gmail.com
Whole thread Raw
In response to Re: documentation issue - extensions  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
2011/12/8 Robert Haas <robertmhaas@gmail.com>:
> On Wed, Dec 7, 2011 at 4:37 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> 2011/12/7 Kevin Grittner <Kevin.Grittner@wicourts.gov>:
>>> Pavel Stehule <pavel.stehule@gmail.com> wrote:
>>>
>>>> I can upgrade - it's not problem - just it is surprise for me -
>>>> because documentation is not related to mayor version. Maybe this
>>>> issue can be documented somewhere
>>>
>>> Don't the release notes, mentioning that the bug is fixed in 9.1.2,
>>> cover that?
>>
>> It is little bit difficult detect this issue as bug
>
> It's not a bug.  It's an not-forward-compatible behavior change in a
> minor release.

so this can be mentioned in documentation elsewhere than release notes
- the best is near related examples - it is different behave than
postgresql's user expect.

I understand to reason now - and it has sense - but it is surprising -
not all has newer postgres - this version is mostly in development
environments than production in this moment.

Regards

Pavel


>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pg_dump --exclude-table-data
Next
From: Tom Lane
Date:
Subject: Lots of FSM-related fragility in transaction commit