Lock table, best option? - Mailing list pgsql-general

From Andre Lopes
Subject Lock table, best option?
Date
Msg-id y2u18f98e681004241346idf8f6948yf69a7a88bee87c9d@mail.gmail.com
Whole thread Raw
Responses Re: Lock table, best option?  (Josh Kupershmidt <schmiddy@gmail.com>)
Re: Lock table, best option?  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-general
Hi,

I need to do a SELECT and an UPDATE, but I will have concurrent processes doing the same task.

How can I prevent that the concurrent task don't have the same results in the SELECT? Locking a table? How can I do that?

Best Regards,

pgsql-general by date:

Previous
From: Oliver Kohll - Mailing Lists
Date:
Subject: Re: Invalid objects
Next
From: Sam
Date:
Subject: Help me stop postgres from crashing.