.
It's surely a noob's question but how can I use a debugger with PostegreSQL?
Regards,
Jonathan Scher
(gdb) file /usr/local/pgsql/bin/postgres
Reading symbols from /usr/local/pgsql/bin/postgres...(no debugging
symbols found)...done.
(gdb) set args -D /home/heziva/pgsql/pgsql_data/
(gdb) b
will upgrade it to exclusive. Then it
would be possible to allow any read-only operation, and to forbid all
operation that would need to upgrade.
I know that there is a sx_try_upgrade function on freeBSD kernel (man
sx), so I guess there is a way to do it, isn't it?
Regards,
Jonathan Scher
constraint, then if
nothing is found, insert it.
- Try to insert a new row, catch if there is any error, and then search
for all tuple matching.
As it would be a new command, I have no idea on what the data could be.
Does syntax meet your needs? Which choice should I implement?
Regards
Jonathan Scher
in the TO-list?
Best regards,
Jonathan Scher
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Tom Lane a écrit :
Jonathan Scher [EMAIL PROTECTED] writes:
CLUSTER uses an ACCESS EXCLUSIVE lock. Why does it forbid concurrent reads?
Because when it drops the old copy of the table there had better not be
any concurrent readers.
regards, tom lane
