| From: | Olivier Gautherot <ogautherot(at)gautherot(dot)net> |
|---|---|
| To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL and local HDD |
| Date: | 2023-08-16 06:12:09 |
| Message-ID: | CAJ7S9TU+R0n7F=66HT7FLcTSJNnFbVHbPfDhvYEXC-nb4VB12w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
El mié, 16 ago 2023 6:54, Ron <ronljohnsonjr(at)gmail(dot)com> escribió:
> On 8/15/23 23:48, Olivier Gautherot wrote:
>
>
> El mié, 16 ago 2023 5:39, Ron <ronljohnsonjr(at)gmail(dot)com> escribió:
>
>> On 8/15/23 04:24, Olivier Gautherot wrote:
>>
>> [snip]
>>
>> Does the database have to be on a storage like EMC or QNAP?
>>>
>>
>> Faster storage can only help but I would start by discarding functional
>> overhead.
>>
>>
>> Functional overhead?
>>
>
> I mean inefficient design, which won't be solved by changing the storage.
>
>
> Ah, the normal aspects of physical design...
>
... and considerung that the OP did not quantify what "slow" means and what
his reference/expectation is.
Let's wait for the OP to give more background.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Russell Rose | Passfield Data Systems | 2023-08-16 06:22:27 | Re: Converting sql anywhere to postgres |
| Previous Message | Ron | 2023-08-16 04:54:35 | Re: PostgreSQL and local HDD |