| From: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Greg Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 9.1.2 ? |
| Date: | 2011-11-09 18:38:35 |
| Message-ID: | 4EBAC8AB.4090503@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/09/2011 01:12 PM, Greg Jaskiewicz wrote:
> Would you consider it a blocker for a rollout on production system ?
I wouldn't. Good process for checking your backups should find this
problem if it pops up, and it's not that easy to run into. That's why I
was saying there are workarounds here, they're just not nice to put
people through.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-11-09 18:42:53 | Re: [COMMITTERS] pgsql: In COPY, insert tuples to the heap in batches. |
| Previous Message | Greg Jaskiewicz | 2011-11-09 18:29:12 | Re: const correctness |