On Wed, Jun 15, 2022 at 4:13 AM Mauro Farracha wrote:
> The scenario:
> - Out of nowhere (during the weekend), without database activity load or
> batches running, with previous nightly run of vacuum freeze, in the middle of
> the day, with xids and mxids below 20M we are seeing autovacuum being
Frankly speaking, Aurora PostgreSQL's behaviour is quite unpredictable.
In our case, the autovacuum was not even getting triggered in spite of
crossing the autovacuum_freeze_max_age. Finally, the database went down
abruptly, which resolved the issue.
Thanks,
Ninad
On Wed, Jun 15, 2022 at 7:57 PM
Peter Eisentraut writes:
> There are also cases where on one system the locale is spelled
> xx_YY.UTF8 and on another xx_YY.UTF-8. If we start adjusting for case,
> should we adjust for this as well? What other cases are there?
> So this would need a bit more research.
Yeah. I would tend to
Hello,
Is it possible to explicitly issue a checkpoint before we move on to the
pg_upgrade command?
so that in the circumstances of the Upgrade issues (like PANIC: could not
locate a valid checkpoint record), we still have this last explicit checkpoint
available.
Please let us know your thoug
On 23.06.22 20:21, Adrian Klaver wrote:
Not sure why that is necessary? Is seems this is low hanging fruit
that could dealt with by the equivalent of lower('en_US.UTF-8') =
lower('en_US.utf-8').
Well that was clear as mud. My point was that I don't see why the end
user should have to do this
On 23.06.22 20:21, Adrian Klaver wrote:
On 6/23/22 10:11, Adrian Klaver wrote:
On 6/23/22 00:37, Tomas Pospisek wrote:
On 22.06.22 22:18, Tomas Pospisek wrote:
On 22.06.22 21:25, Adrian Klaver wrote:
On 6/22/22 12:17, Tomas Pospisek wrote:
So I used both pg_dump and pg_restore from the ne
