On Sun, Jul 7, 2013 at 12:17 PM, Robins Tharakan wrote:
> Updated the patch:
> - Updated ROLEs as per Robert's feedback
You managed to use a naming convention different from the one that you
used before. Before, you had regress_rol_op1; here, you've got
regress_lock_rol1. Consistency may be the
On 23 May 2013 18:19, Robins Tharakan wrote:
> Please find attached a patch to take code-coverage of LOCK TABLE (
> src/backend/commands/lockcmds.c) from 57% to 84%.
Updated the patch:
- Updated ROLEs as per Robert's feedback
- Added test to serial_schedule.
--
Robins Tharakan
regress_lock_v
Hi,
Please find attached a patch to take code-coverage of LOCK TABLE (
src/backend/commands/lockcmds.c) from 57% to 84%.
Any and all feedback is welcome.
--
Robins Tharakan
regress_lock.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To mak
