From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
---|---|
To: | Ian Harding <harding(dot)ian(at)gmail(dot)com> |
Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: How different is AWS-RDS postgres? |
Date: | 2021-05-27 02:04:59 |
Message-ID: | 45421FB2-53B7-4D10-83BC-AC3791E9BA83@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On May 26, 2021, at 4:37 PM, Ian Harding <harding(dot)ian(at)gmail(dot)com> wrote:
>
>
> There is an option to send the logs to cloudwatch which makes it less awful to look at them.
I have that but precious little of interest there. Lots of autovac, a smattering of hints to increase wal size!? I have yet to spot anything which corresponds to the “I/O failure” which the middle ware gets.
I don’t have query logging on, but I do see reports from my psql session fat-fingering.
As to the logs UI, the search is pretty feeble; I don’t understand why there are four channels of logs; the graphs are wearing the same rose-coloured as the logs.
And 24 hours without a peep from AWS support. (I don’t call mailing me what I sent them “contact”.)
My guess right now is that the entire tomcat connection pool is in a single transaction? That’s the only way the tables could disappear. I am making separate calls to JDBC getConnection () for each doPost.
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Semanchuk | 2021-05-27 13:45:30 | Re: How different is AWS-RDS postgres? |
Previous Message | Ian Harding | 2021-05-26 22:37:03 | Re: How different is AWS-RDS postgres? |