>
> The main problem here is that "Amazon Aurora" is not PostgreSQL.
> If I understand Amazon's documentation, what you are using is
> officially named "Amazon Aurora with PostgreSQL Compatibility",
> and that sums is up quite nicely: Aurora is a database engine
> developed at Amazon - and it's in
Thank you Adam and Christoph,
You are totally right, that AWS support is the one to help me with this
problem.
I am in contact with them for quite some time on this problem and as there
was no progress on resolving this,
I tried to find some insight or trick that I missed here. It's a long shot
(:
## Chris Borckholder (chris.borckhol...@bitpanda.com):
> We are experiencing a strange situation with an AWS Aurora postgres
> instance.
The main problem here is that "Amazon Aurora" is not PostgreSQL.
If I understand Amazon's documentation, what you are using is
officially named "Amazon Aurora w
I would highly suggest you reach out to AWS support for Aurora questions,
that's part of what you're paying for, support.
For reasons you mentioned and more, it's pretty hard to debug issues
because it isn't actually Postgres.
>
Thanks for your insight!
I cannot find any errors related to archiving in the logs that are
accessible to me.
It's definitely something that I will forward to the support team of the
managed database.
Best Regards
Chris
On Thu, Aug 6, 2020 at 3:18 AM Mohamed Wael Khobalatte <
mkhobala...@grubhub
Thank you for your insight Seenu!
That is a good point, unfortunately we do not have access to the
server/file system as the database is a managed service.
Access to the file system from postgres like pg_ls_dir is also blocked.
Are you aware of another, creative way to infer the wal file size fro
On Tue, Aug 4, 2020 at 4:39 AM Chris Borckholder <
chris.borckhol...@bitpanda.com> wrote:
> Hi!
>
> We are experiencing a strange situation with an AWS Aurora postgres
> instance.
> The database steadily grows in size, which is expected and normal.
> After enabling logical replication, the disk us
There may be lot of wal files or the size of log files in pg_log might be
huge. "du -sh *" of data directory holding the database might help.
Regards,
Seenu.
On Tue, Aug 4, 2020 at 2:09 PM Chris Borckholder <
chris.borckhol...@bitpanda.com> wrote:
> Hi!
>
> We are experiencing a strange situat
Hi!
We are experiencing a strange situation with an AWS Aurora postgres
instance.
The database steadily grows in size, which is expected and normal.
After enabling logical replication, the disk usage reported by AWS metrics
increases much faster then the database size (as seen by \l+ in psql). The
