Re: Massive table (500M rows) update nightmare

My bad - I thought I had, so it has been re-posted with a (v2) disclaimer in
the title... like THAT will stop the flaming! <g>

Thanks for your patience!

"Craig James" <craig_james(at)emolecules(dot)com> wrote in message
news:4B4F8A49(dot)7010906(at)emolecules(dot)com(dot)(dot)(dot)
> Carlo Stonebanks wrote:
>> Guys, I want to thank you for all of the advice - my client has just made
>> a surprise announcement that he would like to set start from scratch with
>> a new server, so I am afraid that all of this great advice has to be seen
>> in the context of whatever decision is made on that. I am out there,
>> hat-in-hand, looking for advice under the PERFORM post: "New server to
>> improve performance on our large and busy DB - advice?"
>
> You might start this as a new topic with a relevant title, and reiterate
> your database requirements. Otherwise it will get submerged as just a
> footnote to your original question. It's really nice to be able to
> quickly find the new-equipment discussions.
>
> Craig
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>