Hi, On Thu, 05 Aug 2010 17:52:44 +0900 노현석 wrote: > we test locking PostgreSQL 8.4.4 on x86_64. > [...] > begin; > delete from citytest; > <------- no commit/rollback > <------- this will be Blocker > > 2> session 2,3,4 > ########################### > $ psql mydb > delete from citytest; > <--- waiting > <--- these are blocked.... [...] > Could you teach me, Is this expected behavior ?? (disapper blocking > process not only Blocker process) and > Could you teach me, how can we eliminate just Blocker session... Note: the cause for the blocked sessions is in your first session. By deleting all entries from table "citytest", PG will lock all deleted entries. Once you try to delete one or all of this rows in another session, PG waits until the first session is either committed or rolled back. This is expected behaviour. Bye -- Andreas 'ads' Scherbaum Failure is not an option. It comes bundled with your Microsoft product. (Ferenc Mantfeld) -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
