Yes, this is a known issue due to the fact that the triggers use SPI and need to use SELECT ... FOR UPDATE to lock the rows it is reading (and select for update requires the update permission). The workaround I know about for now is to give update permission and make triggers to disallow updates as appropriate. (If this isn't in the TODO list or FAQ yet, it probably should be.) Stephan Szabo [EMAIL PROTECTED] On Wed, 23 Aug 2000 [EMAIL PROTECTED] wrote: > NAGY Andras ([EMAIL PROTECTED]) reports a bug with a severity of 3 > The lower the number the more severe it is. > > Short Description > Foreign keys referencing read-only tables fail
- [BUGS] PostgreSQL BugTool Submission pgsql-bugs
- [BUGS] PostgreSQL BugTool Submission pgsql-bugs
- [BUGS] PostgreSQL BugTool Submission pgsql-bugs
- [BUGS] PostgreSQL BugTool Submission pgsql-bugs
- [BUGS] PostgreSQL BugTool Submission pgsql-bugs
- [BUGS] PostgreSQL BugTool Submission pgsql-bugs
- [BUGS] PostgreSQL BugTool Submission pgsql-bugs
- [BUGS] PostgreSQL BugTool Submission pgsql-bugs
- [BUGS] PostgreSQL BugTool Submission Stephan Szabo
- [BUGS] PostgreSQL BugTool Submission pgsql-bugs
- Re: [BUGS] PostgreSQL BugTool Submission Bruce Momjian
- Re: [BUGS] PostgreSQL BugTool Submission Stephan Szabo
- Re: [BUGS] PostgreSQL BugTool Submission Bruce Momjian
- Re: [BUGS] PostgreSQL BugTool Submission Stephan Szabo
- Re: [BUGS] PostgreSQL BugTool Submission Philip Warner