On 11/7/18 1:59 AM, Amit Langote wrote:
> * Ensure that automatically created child indexes are created in the same
Thanks, that is much clearer. I have made that update.
Thanks again for your help!
Jonathan
2018-11-08 Cumulative Update
The PostgreSQL Global Develop
Hi,
On 2018/11/07 13:08, Jonathan S. Katz wrote:
> Thanks. I left it as "Fix several crashes with triggers" - please see
> attached.
Thank you. Just one more comment on the top sentence.
* Ensure that if a parent partition has an index created in a tablespace,
then all child indexes will be cre
On Wed, Nov 07, 2018 at 02:06:13AM +, Andrew Gierth wrote:
> So the minimum recovery location is recorded as 0x201FCFE0, but there
> are data pages on disk with LSNs as recent as 0x25BAFE80. That's a whole
> lot of daylight that could contain a btree delete.
Sorry for the time it took. I was
On 11/6/18 9:35 PM, Amit Langote wrote:
> On 2018/11/07 11:28, Noah Misch wrote:
>> On Mon, Nov 05, 2018 at 10:49:30PM -0500, Jonathan S. Katz wrote:
>>> On 11/5/18 9:58 PM, Amit Langote wrote:
On 2018/11/06 11:25, Noah Misch wrote:
> On Mon, Nov 05, 2018 at 04:01:59PM -0500, Jonathan S. K
On 2018/11/07 11:28, Noah Misch wrote:
> On Mon, Nov 05, 2018 at 10:49:30PM -0500, Jonathan S. Katz wrote:
>> On 11/5/18 9:58 PM, Amit Langote wrote:
>>> On 2018/11/06 11:25, Noah Misch wrote:
On Mon, Nov 05, 2018 at 04:01:59PM -0500, Jonathan S. Katz wrote:
> Attached is a draft of the pr
On Mon, Nov 05, 2018 at 10:49:30PM -0500, Jonathan S. Katz wrote:
> On 11/5/18 9:58 PM, Amit Langote wrote:
> > On 2018/11/06 11:25, Noah Misch wrote:
> >> On Mon, Nov 05, 2018 at 04:01:59PM -0500, Jonathan S. Katz wrote:
> >>> Attached is a draft of the press release for review. Please let me know
> "Michael" == Michael Paquier writes:
>> So while there _probably_ isn't any data corruption, the standby can
>> get into a state that isn't restartable unless you know to block
>> client connections to it until it has caught up. Rebuilding the
>> standby from the master will work but th
On Tue, Nov 06, 2018 at 11:44:56PM +, Andrew Gierth wrote:
> The commit message doesn't really show the severity of the problem at
> all.
I take the blame for that. And my apologies for what it's worth.
> The users whose case I was diagnosing on IRC were finding that their
> monitoring syste
> "Tom" == Tom Lane writes:
Tom> You could be bit by any shutdown of the old code, no, whether it's
Tom> part of a pg_upgrade or not?
Nothing to do with pg_upgrade, this is likely to bite people just doing
an update from the previous minor release.
Tom> Also, it looks like the bug only a
Stephen Frost writes:
> * Andrew Gierth (and...@tao11.riddles.org.uk) wrote:
>> Do we need to add anything in the release notes about possible
>> complications in upgrading caused by the 65f39408ee71 / 56535dcdc9e2
>> issue?
>>
>> If upgrading from the immediately prior point releases to this one
Greetings,
* Andrew Gierth (and...@tao11.riddles.org.uk) wrote:
> Do we need to add anything in the release notes about possible
> complications in upgrading caused by the 65f39408ee71 / 56535dcdc9e2
> issue?
>
> If upgrading from the immediately prior point releases to this one, then
> the shutd
On 11/5/18 11:10 PM, Amit Langote wrote:
> Hi,
>
> On 2018/11/06 12:49, Jonathan S. Katz wrote:
>>
>> I still feel inclined to elaborate on the "Prevent creation of a
>> partition in a trigger attached to its parent table" but perhaps in
>> future release we will just mention that this behavior is
Do we need to add anything in the release notes about possible
complications in upgrading caused by the 65f39408ee71 / 56535dcdc9e2
issue?
If upgrading from the immediately prior point releases to this one, then
the shutdown of the previous version might have left an incorrect min
recovery point i
Hi,
On 2018/11/06 12:49, Jonathan S. Katz wrote:
> On 11/5/18 9:58 PM, Amit Langote wrote:
>> On 2018/11/06 11:25, Noah Misch wrote:
>>> On Mon, Nov 05, 2018 at 04:01:59PM -0500, Jonathan S. Katz wrote:
Attached is a draft of the press release for review. Please let me know
if there are
On 11/5/18 9:58 PM, Amit Langote wrote:
> On 2018/11/06 11:25, Noah Misch wrote:
>> On Mon, Nov 05, 2018 at 04:01:59PM -0500, Jonathan S. Katz wrote:
>>> Attached is a draft of the press release for review. Please let me know
>>> if there are any corrections/suggestions.
>>> * Disallows the creatio
On 2018/11/06 11:25, Noah Misch wrote:
> On Mon, Nov 05, 2018 at 04:01:59PM -0500, Jonathan S. Katz wrote:
>> Attached is a draft of the press release for review. Please let me know
>> if there are any corrections/suggestions.
>> * Disallows the creation of a new partition from a trigger that is at
On Mon, Nov 05, 2018 at 04:01:59PM -0500, Jonathan S. Katz wrote:
> Attached is a draft of the press release for review. Please let me know
> if there are any corrections/suggestions.
> This update is also the final release for PostgreSQL 9.3, which is now
> end-of-life and will no longer receive
On 11/2/18 8:14 PM, Tom Lane wrote:
> I've made a pass over the commit log up to now, and prepared draft
> release note entries for everything that seemed worth documenting;
> see
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=65a82a7649860f8010db581a0d1f12aa92f5969b
>
> A
18 matches
Mail list logo
