| From: | aditya desai <admad123(at)gmail(dot)com> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com>, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |
| Date: | 2021-04-03 14:59:22 |
| Message-ID: | CAN0SRDHd5+vVGUT=5XHnag4mPkyZtMFpVFDzzi8+tA4F6Fwd0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Hi Michael,
Thanks for your response.
Is this table partitioned? - No
How long ago was migration done? - 27th March 2021
Has vacuum freeze and analyze of tables been done? - We ran vacuum analyze.
Was index created after populating data or reindexed after perhaps? -
Index was created after data load and reindex was executed on all tables
yesterday.
Version is PostgreSQL-11
Regards,
Aditya.
On Sat, Apr 3, 2021 at 7:40 PM Michael Lewis <mlewis(at)entrata(dot)com> wrote:
> It seems like something is missing. Is this table partitioned? How long
> ago was migration done? Has vacuum freeze and analyze of tables been done?
> Was index created after populating data or reindexed after perhaps? What
> version are you using?
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2021-04-03 15:04:17 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |
| Previous Message | Zhihong Yu | 2021-04-03 14:38:50 | Re: TRUNCATE on foreign table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2021-04-03 15:04:17 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |
| Previous Message | Justin Pryzby | 2021-04-03 14:16:51 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |