| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org, KK CHN <kkchn(dot)in(at)gmail(dot)com> |
| Subject: | Re: PostgreSQL Server Hang |
| Date: | 2023-06-22 05:39:19 |
| Message-ID: | D296CB7C-C214-4EF4-B328-3514FF3E6248@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 22 June 2023 07:09:26 CEST, KK CHN <kkchn(dot)in(at)gmail(dot)com> wrote:
>*Description of System: *
>1. We are running a Postgres Server (version 12, on CentOS 6) for an
>emergency call attending and vehicle tracking system fitted with mobile
>devices for vehicles with navigation apps for emergency service.
>
>2. vehicles every 30 Seconds sending location coordinates( Lat /Long ) and
>getting stored into the DB server at the emergency call center cum control
>room.
>
>*Issue: *
>We are facing an issue of the database hanging and becoming unresponsive
>for
>applications running which try to connect to the DB.
>
>*Question: *
>How to optimize and fine tune this database performance issue ? Definitely
>pouring the resources like the above is not a solution.
>
>What to check the root cause and find for the performance bottle neck
>reasons ?
>
Have you THP disabled?
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dominique Devienne | 2023-06-22 08:22:41 | Catalog for LISTEN'ed to notification channels? |
| Previous Message | KK CHN | 2023-06-22 05:09:26 | PostgreSQL Server Hang |