> Using "IF NOT EXISTS" would not solve this problem > in a high concurrency scenario.
Thanks for your feedback. > There would still be a race condition within the > Postgres internal functions. Are there any chances that this database software implementation will become robust and safe against the discussed race condition? > Have you tried using savepoints? I am going to use a serial database preparation step instead for my application so that the corresponding tables will be explicitly deleted and created by a small SQL script. Regards, Markus -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
