agora inbox for pgsql-sql@postgresql.org  
help / color / mirror / Atom feed
Apparently table locks are the key issue to see red flags
6+ messages / 4 participants
[nested] [flat]

* Apparently table locks are the key issue to see red flags
@ 2022-03-16 20:14  Shaozhong SHI <shishaozhong@gmail.com>
  0 siblings, 2 replies; 6+ messages in thread

From: Shaozhong SHI @ 2022-03-16 20:14 UTC (permalink / raw)
  To: pgsql-sql <pgsql-sql@lists.postgresql.org>

Apparently table locks are the key issue to see red flags.

As we observe, every time, red marking occurs, there must be some tables
are locked.

Can anyone shed light into this?

Regards,

David

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Apparently table locks are the key issue to see red flags
@ 2022-03-16 20:15  Shaozhong SHI <shishaozhong@gmail.com>
  parent: Shaozhong SHI <shishaozhong@gmail.com>
  1 sibling, 2 replies; 6+ messages in thread

From: Shaozhong SHI @ 2022-03-16 20:15 UTC (permalink / raw)
  To: pgsql-general <pgsql-general@lists.postgresql.org>

Apparently table locks are the key issue to see red flags.

As we observe, every time, red marking occurs, there must be some tables
are locked.

Can anyone shed light into this?

Regards,

David

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Apparently table locks are the key issue to see red flags
@ 2022-03-16 20:21  Ron <ronljohnsonjr@gmail.com>
  parent: Shaozhong SHI <shishaozhong@gmail.com>
  1 sibling, 0 replies; 6+ messages in thread

From: Ron @ 2022-03-16 20:21 UTC (permalink / raw)
  To: pgsql-general@lists.postgresql.org

On 3/16/22 15:15, Shaozhong SHI wrote:
>
>
> Apparently table locks are the key issue to see red flags.
>
> As we observe, every time, red marking occurs, there must be some tables 
> are locked.

Where do these red markings occur?  (It is physically impossible for them to 
occur in Postgresql because Postgresql is a daemon, and therefore does not 
have a GUI.)

-- 
Angular momentum makes the world go 'round.

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Apparently table locks are the key issue to see red flags
@ 2022-03-16 20:23  Adrian Klaver <adrian.klaver@aklaver.com>
  parent: Shaozhong SHI <shishaozhong@gmail.com>
  1 sibling, 0 replies; 6+ messages in thread

From: Adrian Klaver @ 2022-03-16 20:23 UTC (permalink / raw)
  To: Shaozhong SHI <shishaozhong@gmail.com>; pgsql-general <pgsql-general@lists.postgresql.org>

On 3/16/22 13:15, Shaozhong SHI wrote:
> 
> 
> Apparently table locks are the key issue to see red flags.
> 
> As we observe, every time, red marking occurs, there must be some tables 
> are locked.
> 
> Can anyone shed light into this?

Not with the information provided.

Needed info(and you should know this by now):

1) Postgres version

2) Definition of red flags?

3) How do you observe the tables locked?

4) The results of the process you use in 3)

> 
> Regards,
> 
> David


-- 
Adrian Klaver
adrian.klaver@aklaver.com





^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Apparently table locks are the key issue to see red flags
@ 2022-03-16 20:32  Shaozhong SHI <shishaozhong@gmail.com>
  parent: Shaozhong SHI <shishaozhong@gmail.com>
  1 sibling, 1 reply; 6+ messages in thread

From: Shaozhong SHI @ 2022-03-16 20:32 UTC (permalink / raw)
  To: Pgsql-admin <pgsql-admin@postgresql.org>

Apparently table locks are the key issue to see red flags.

As we observe, every time, red marking occurs, there must be some tables
are locked.

Can anyone shed light into this?

Regards,

David

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Apparently table locks are the key issue to see red flags
@ 2022-03-17 13:21  Jayson Hreczuck <jayson.hreczuck@studentuniverse.com>
  parent: Shaozhong SHI <shishaozhong@gmail.com>
  0 siblings, 0 replies; 6+ messages in thread

From: Jayson Hreczuck @ 2022-03-17 13:21 UTC (permalink / raw)
  To: Shaozhong SHI <shishaozhong@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@postgresql.org>

Need more detail on this.  Locks are generally caused by long updates or
writes or perhaps a hung transaction. Can you reply with a bit more detail
of what you are seeing, perhaps pg_stat_activity list?

Rule of thumb for high trx environments is to batch updates especially for
larger tables to avoid excessive locking.

On Wed, Mar 16, 2022 at 4:32 PM Shaozhong SHI <shishaozhong@gmail.com>
wrote:

>
> Apparently table locks are the key issue to see red flags.
>
> As we observe, every time, red marking occurs, there must be some tables
> are locked.
>
> Can anyone shed light into this?
>
> Regards,
>
> David
>


-- 


*Jayson Hreczuck | Principal Database AdministratorC: +1 617.571.9861*130
Turner St, Ste 530, Waltham, MA 02453

^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2022-03-17 13:21 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-03-16 20:14 Apparently table locks are the key issue to see red flags Shaozhong SHI <shishaozhong@gmail.com>
2022-03-16 20:15 ` Shaozhong SHI <shishaozhong@gmail.com>
2022-03-16 20:21   ` Ron <ronljohnsonjr@gmail.com>
2022-03-16 20:23   ` Adrian Klaver <adrian.klaver@aklaver.com>
2022-03-16 20:32 ` Shaozhong SHI <shishaozhong@gmail.com>
2022-03-17 13:21   ` Jayson Hreczuck <jayson.hreczuck@studentuniverse.com>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox