On Tue, Oct 13, 2015 at 10:37 PM, dinesh kumar <dineshkuma...@gmail.com> wrote: > In an existing wait policies like WAIT(default) and NO WAIT, > one can be sure to determine(Using ROW_COUNT daignostics counter), > how many required tuples he processed in a transaction. > But this is not case when it comes to SKIP LOCKED.
Sure it is. You didn't process the ones that you skipped. This is no different than if you say WHERE a = 5. Depending on plan choice and table contents, you may have "skipped" a large number of rows where a != 5, or you may have skipped none at all. > In my view, SKIP LOCKED is a nice feature, which gives only the available OR > unlocked tuples. > But those are not the complete required tuples for the given SQL statement. > Isn't it ?! They better be. If you wanted the locked tuples, you shouldn't have asked to skip them. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
