On 2012-11-27 10:08:12 -0800, Jeff Janes wrote:
> Doing PITR in 9.2.1, the system claims that it reached a consistent
> recovery state immediately after redo starts.
> This leads to it various mysterious failures, when it should instead
> throw a "requested recovery stop point is before consistent
On 28.11.2012 06:27, Noah Misch wrote:
On Tue, Nov 27, 2012 at 10:08:12AM -0800, Jeff Janes wrote:
Doing PITR in 9.2.1, the system claims that it reached a consistent
recovery state immediately after redo starts.
This leads to it various mysterious failures, when it should instead
throw a "reque
On 28.11.2012 15:26, Andres Freund wrote:
Hm. Are you sure its actually reading your backup file? Its hard to say
without DEBUG1 output but I would tentatively say its not reading it at
all because the the "redo starts at ..." message indicates its not using
the checkpoint location from the backu
On 2012-11-28 15:37:38 +0200, Heikki Linnakangas wrote:
> On 28.11.2012 15:26, Andres Freund wrote:
> >Hm. Are you sure its actually reading your backup file? Its hard to say
> >without DEBUG1 output but I would tentatively say its not reading it at
> >all because the the "redo starts at ..." messa
On 28.11.2012 15:47, Andres Freund wrote:
I mean the label read by read_backup_label(). Jeff's mail indicated it
had CHECKPOINT_LOCATION at 1/188D8120 but redo started at 1/CD89E48.
That's correct. The checkpoint was at 1/188D8120, but it's redo pointer
was earlier, at 1/CD89E48, so that's whe
On 2012-11-28 16:34:55 +0200, Heikki Linnakangas wrote:
> On 28.11.2012 15:47, Andres Freund wrote:
> >I mean the label read by read_backup_label(). Jeff's mail indicated it
> >had CHECKPOINT_LOCATION at 1/188D8120 but redo started at 1/CD89E48.
>
> That's correct. The checkpoint was at 1/188D8120
The following bug has been logged on the website:
Bug reference: 7710
Logged by: Tarvi Pillessaar
Email address: tar...@gmail.com
PostgreSQL version: 9.1.6
Operating system: linux
Description:
This happens only if wal_level=hot_standby.
Here are the steps to reprodu
Heikki Linnakangas writes:
> On 28.11.2012 06:27, Noah Misch wrote:
>> I observed a similar problem with 9.2. Despite a restore_command that failed
>> every time, startup from a hot backup completed. At the time, I suspected a
>> mistake on my part.
> I believe this was caused by this little ty
On Wed, Nov 28, 2012 at 5:37 AM, Heikki Linnakangas
wrote:
> On 28.11.2012 15:26, Andres Freund wrote:
>>
>
>
>> Can you reproduce the issue? If so, can you give an exact guide? If not,
>> do you still have the datadir et al. from above?
Yes, it is reliable enough to be used for "git bisect"
rm
On Wed, Nov 28, 2012 at 7:51 AM, Tom Lane wrote:
> Heikki Linnakangas writes:
>> On 28.11.2012 06:27, Noah Misch wrote:
>>> I observed a similar problem with 9.2. Despite a restore_command that
>>> failed
>>> every time, startup from a hot backup completed. At the time, I suspected a
>>> mista
The following bug has been logged on the website:
Bug reference: 7711
Logged by: Michael Kolomeitsev
Email address: mkolomeit...@gmail.com
PostgreSQL version: 9.2.1
Operating system: Arch Linux
Description:
It seems multiple dots (".") are not allowed. For example: a.
Hello
it is not a bug - it is known limit :(
nested structures are not supported as target
anybody can implement it if like it
Regards
Pavel Stehule
2012/11/29 :
> The following bug has been logged on the website:
>
> Bug reference: 7711
> Logged by: Michael Kolomeitsev
> Email
12 matches
Mail list logo
