| From: | Jehan-Guillaume de Rorthais <ioguix(at)free(dot)fr> |
|---|---|
| To: | Emre Hasegeli <emre(at)hasegeli(dot)com> |
| Cc: | Sterpu Victor <victor(at)caido(dot)ro>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Unique values on multiple tables |
| Date: | 2016-03-28 13:17:44 |
| Message-ID: | 20160328151744.7b8fa6c2@firost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le Mon, 28 Mar 2016 12:44:51 +0200,
Emre Hasegeli <emre(at)hasegeli(dot)com> a écrit :
> > Could I use lock tables to fix this? Is postgres automaticaly locking a
> > table while running a trigger on that table?
>
> You can use LOCK TABLE. See the documentation:
>
> http://www.postgresql.org/docs/current/static/explicit-locking.html
Use advisory locks for better performance. See the following article (at
least the two lasts chapters) for some examples:
http://blog.ioguix.net/postgresql/2015/02/05/Partitionning-and-constraints-part-1.html
Cheers,
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2016-03-28 13:45:03 | Re: View deleted records in a table |
| Previous Message | Roman Scherer | 2016-03-28 11:36:19 | How to quote the COALESCE function? |