On Thursday, June 29, 2017, Ken Tanzer wrote:
>
> I think it's great and impressive that you can install and run two
> versions simultaneously, but I have found a couple gotchas in the process.
> Maybe those are documented somewhere, but if so I haven't seen it. The
>
On Thu, Jun 29, 2017 at 9:34 AM, Jeff Janes wrote:
>
>> Well sure, I can see it increases your chances of getting _something_
>> restored. But there's also a lot to be said for ensuring that _all_ your
>> data restored, and did so correctly, no?
>>
>
> Record the errors,
On Thu, Jun 29, 2017 at 12:05 AM, Ken Tanzer wrote:
> Thanks for the responses. For me, using the 9.2 binary was the winner.
> Shoulda thought of that!
>
> On Wed, Jun 28, 2017 at 1:30 PM, Tom Lane wrote:
>
>>
>> Generally speaking, it helps a lot if
On 06/29/2017 12:05 AM, Ken Tanzer wrote:
Thanks for the responses. For me, using the 9.2 binary was the winner.
Shoulda thought of that!
On Wed, Jun 28, 2017 at 1:30 PM, Tom Lane > wrote:
Generally speaking, it helps a lot if you don't
Thanks for the responses. For me, using the 9.2 binary was the winner.
Shoulda thought of that!
On Wed, Jun 28, 2017 at 1:30 PM, Tom Lane wrote:
>
> Generally speaking, it helps a lot if you don't insist on restoring the
> output in a single transaction. In this case, that
Alvaro Herrera writes:
> Ken Tanzer wrote:
>> I didn't see any options for dealing with this, though I'm hoping I'm
>> missing something easy or obvious. Any suggestions or help would be
>> appreciated. Thanks.
> pg_dump doesn't promise that its output is compatible
On Wednesday, June 28, 2017, Alvaro Herrera
wrote:
> Ken Tanzer wrote:
>
> > I didn't see any options for dealing with this, though I'm hoping I'm
> > missing something easy or obvious. Any suggestions or help would be
> > appreciated. Thanks.
>
> pg_dump doesn't
Ken Tanzer wrote:
> I didn't see any options for dealing with this, though I'm hoping I'm
> missing something easy or obvious. Any suggestions or help would be
> appreciated. Thanks.
pg_dump doesn't promise that its output is compatible with servers older
than itself. I'm afraid you're stuck
Hi. I've got a CentOS server with 9.2 and 9.6 both running. (Both from
PGDG). I've got a cron job that transfers data from one DB to another,
that recently stopped working, and I traced it to my installing 9.6. The
dump comand is pretty straightforward:
pg_dump -c -O -t "${prefix}*"...
But