Ok, I believe I have found an explanation, and it is due to a logic error,
not due to anything funky happening with the database. Please excuse the
noise.
Steve
On Tue, Mar 30, 2021 at 11:06 AM Steve Baldwin
wrote:
> Thanks Adrian. This is 'vanilla' postgres as far as I know (unlike their
>
RDS is also a modified version of Postgresql, just not as modified as Aurora.
On 3/29/21 7:06 PM, Steve Baldwin wrote:
Thanks Adrian. This is 'vanilla' postgres as far as I know (unlike their
postgres-flavoured Aurora product).
b2bc_owner@b2bcreditonline=> select version();
Thanks Adrian. This is 'vanilla' postgres as far as I know (unlike their
postgres-flavoured Aurora product).
b2bc_owner@b2bcreditonline=> select version();
version
On 3/29/21 4:39 PM, Steve Baldwin wrote:
Hi all,
I know this is going to sound weird/unbelievable, but I'm trying to come
up with an explanation for what I've observed.
First, a couple of data points. The instance is running on AWS RDS and
is on version 13.1. All my timestamps and elapsed
Hi all,
I know this is going to sound weird/unbelievable, but I'm trying to come up
with an explanation for what I've observed.
First, a couple of data points. The instance is running on AWS RDS and is
on version 13.1. All my timestamps and elapsed times were taken from the
postgres log
