Re: pg_restore COPY error handling

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org
Subject: Re: pg_restore COPY error handling
Date: 2006-02-01 22:20:49
Message-ID: 20060201222049.GI4474@ns.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

* Bruce Momjian (pgman(at)candle(dot)pha(dot)pa(dot)us) wrote:
> Stephen Frost wrote:
> > Great! It'd be really nice to have this fix in 8.1.3... :)
>
> No, it will not be in 8.1.3. It is a new feature.

I'd really appriciate it if you could review my post to pgsql-bugs,
Message-ID: <20060120144957(dot)GG6026(at)ns(dot)snowman(dot)net>. If this patch is
considered a new feature then I'd like to either revisit that decision
or be given some direction on what a bug-fix patch for the grows-to-3G
bug would look like.

Thanks,

Stephen

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-02-01 22:48:49 Re: pg_restore COPY error handling
Previous Message Greg Sabino Mullane 2006-02-01 19:26:29 Re: New pg_dump options: exclude tables/schemas, multiple