Marc, thanks for the answer. Na, these seem not to be enough universal and easy to hook into existing truncation strategies used in Ruby world. On Fri, Jul 6, 2012 at 6:24 PM, Marc Mamin <M.Mamin@xxxxxxxxxxxx> wrote: > > > > Stanislaw Pankevich wrote: >>>> ==== PostgreSQL db, 30 tables with number of rows < 100 (not huge) - the >>>> fastest way to clean each >>>> non-empty table and reset unique identifier column of empty ones ==== > > Hello, > > 2 'exotic' ideas: > > - use dblink_send_query to do the job in multiple threads (I doubt this > really could be faster) > - have prepared empty tables in a separate schema, and a "garbage schema": > > ALTER TABLE x set schema garbage; > ALTER TABLE prepared.x set schema "current"; > > you should be ready for the next test, > > but still have to clean garbage nad moved to prepared for the next but one > in the background.... > > best regards, > > Marc Mamin -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
