From: | cowwoc <cowwoc(at)bbs(dot)darktech(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Feature request: temporary schemas |
Date: | 2014-09-17 17:11:49 |
Message-ID: | 1410973909239-5819359.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi guys,
I wanted to update you on this topic. Pete provided an excellent answer at
http://dba.stackexchange.com/a/76661/4719 that almost worked (we couldn't
find a solution for functions) but it turns out that my original problem
definition was incorrect.
I assumed that my unit tests only use one connection but upon implementing
the aforementioned solution I discovered that while the client-side is
single threaded, the server-side actually spawns off one database connection
per request, where each test fires multiple requests. It's somewhat obvious
in retrospect, but I hadn't thought of it :)
I further discovered that the database migration tool I am using (Flyway)
supports placeholders
(http://flywaydb.org/documentation/faq.html#placeholders) so I plan on using
that to create UNLOGGED tables for tests and normal tables in production.
Thank you for your patience and your thoughtful feedback!
Gili
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Feature-request-temporary-schemas-tp5819001p5819359.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Dev Kumkar | 2014-09-17 18:20:29 | Re: Regarding timezone |
Previous Message | Martin Waite | 2014-09-17 16:52:25 | Re: encoding confusion with \copy command |