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.