On 19.10.2010 08:51, Fujii Masao wrote:
On Tue, Oct 19, 2010 at 7:00 AM, Jeff Davis wrote:
Do users have any expectation that they can restore a backup without
using recovery.conf by merely having the WAL segments in pg_xlog?
I would expect that to work.
What's the use case?
Creating a st
On Tue, Oct 19, 2010 at 5:18 PM, Heikki Linnakangas
wrote:
> On 19.10.2010 08:51, Fujii Masao wrote:
>>
>> On Tue, Oct 19, 2010 at 7:00 AM, Jeff Davis wrote:
>
> Do users have any expectation that they can restore a backup without
> using recovery.conf by merely having the WAL segment
On 18.10.2010 01:48, Jeff Davis wrote:
On Fri, 2010-10-15 at 15:58 -0700, Jeff Davis wrote:
I don't have a fix yet, because I think it requires a little discussion.
For instance, it seems to be dangerous to assume that we're starting up
from a backup with access to the archive when it might have
The following bug has been logged online:
Bug reference: 5717
Logged by: Richard Huxton
Email address: d...@archonet.com
PostgreSQL version: 9.0.1
Operating system: linux
Description:Domain as array of numeric/varchar does not respect
limits
Details:
Summary: you ca
On Tue, 2010-10-19 at 12:26 +0300, Heikki Linnakangas wrote:
> >1. If reading a checkpoint from the backup_label location, verify that
> > the REDO location for that checkpoint exists in addition to the
> > checkpoint itself. If not, elog with a FATAL immediately.
>
> Makes sense. I wonder if
"Andrew Tipton" writes:
> Attempting to execute an UPDATE that joins to another table where the join
> condition is comparing a composite type fails with the (presumably internal)
> error message "psql:testcase.sql:29: ERROR: could not find pathkey item to
> sort".
Fixed, thanks for the report!
On Tue, 2010-10-19 at 09:51 -0700, Jeff Davis wrote:
> On Tue, 2010-10-19 at 12:26 +0300, Heikki Linnakangas wrote:
> > Excluding pg_xlog is just a recommendation at the moment, though, so we
> > would need a big warning in the docs. And some way to enforce that
> > just_kidding is not included i
On Tue, Oct 19, 2010 at 5:26 AM, Heikki Linnakangas
wrote:
> The fundamental problem is that by definition, a base backup is completely
> indistinguishable from the data directory in the original server. Or is it?
> We recommend that you exclude the files under pg_xlog from the backup. So we
> cou
On Mon, Oct 11, 2010 at 7:50 PM, Tom Lane wrote:
> "Andreas Karlsson" writes:
>> I was looking at the code to see how one would improve indexing of the inet
>> types and saw an inconsistency between the compressed format
>> (gbt_inet_compress) and how network_cmp_internal works. The btree_gist
>>
Robert Haas writes:
> On Mon, Oct 11, 2010 at 7:50 PM, Tom Lane wrote:
>> Well, actually the btree_gist implementation for inet is a completely
>> broken piece of junk: it thinks that convert_network_to_scalar is 100%
>> trustworthy and can be used as a substitute for the real comparison
>> funct
10 matches
Mail list logo
