Re: could not write to log file: No space left on device -> AWS RDS Aurora postgreql DB

Поиск
Список
Период
Сортировка
От dbatoCloud Solution
Тема Re: could not write to log file: No space left on device -> AWS RDS Aurora postgreql DB
Дата
Msg-id CAEz7P_tC4Tu8axpoxq9p9P30Fke2-S7i4Px4K1-kGW_zYtbhEw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: could not write to log file: No space left on device -> AWS RDS Aurora postgreql DB  (naveen goswami <rilogical@gmail.com>)
Список pgsql-admin
Дерево обсуждения
at this movement, we don't have the budget to go higher version, we are planning to use temporary_tablespace and make it default and then try to release the space from tempfiles.

 

 

Thanks & Best Wishes,

Ashok

 

---------------------------------------------------------------------------------------------------------------------

Ashokkumar Mani  (OCP12c/11g/10g/9i, AWS SAA, M103)

Dubai , UAE | BLR , INDIA

M: +971 54 723 0075 | +91 90086 70302 | WApp : +91 81975 99922

W: https://dbatocloudsolution.blogspot.in/ | E: dbatocloud17@gmail.com



On Tue, Feb 2, 2021 at 7:57 AM naveen goswami <rilogical@gmail.com> wrote:
Another option if you cannot change the workload,  Free Local storage (temporary files storage), is twice the size of RAM of your Aurora instance. e.g. r5.db24xlarge will provide 1500GB of free local storage. not sure if its possible, but higher instance size may help but that comes with higher cost.

On Mon, Feb 1, 2021 at 6:11 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Mon, 2021-02-01 at 19:27 +0530, dbatoCloud Solution wrote:
> Is there any way to reduce the temporary files which are having huge size .

Cancel the queries that generate them.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com



В списке pgsql-admin по дате отправления:

Предыдущее
От: naveen goswami
Дата:
Сообщение: Re: could not write to log file: No space left on device -> AWS RDS Aurora postgreql DB
Следующее
От: dbatoCloud Solution
Дата:
Сообщение: Changes in Aurora PostgreSQL for min & max_wal_size parameter