t;
ClientWrite means Postgres is waiting on the *network* sending the
reply back to the client, it is unrelated to I/O. So either your
client isn't consuming the response fast enough, or the network
between them is too slow or shaped.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: http
On Thu, Oct 29, 2020 at 9:43 AM Ehrenreich, Sigrid
wrote:
>
> Hi Tom,
>
> Thanks a lot for your help!
>
> If it is in the HEAD, does it mean, it will be included in v14?
Yes, that's precisely what it means. Unless someone finds something
bad with it and it has to be removed of course, but in
’ version of Postgres 11.6 (“Aurora”) which of course might
> make a difference.
>
Yes, it definitely makes a difference. For Aurora questions you are more
likely to get good answers in the AWS forums rather than the PostgreSQL
ones. It's different from PostgreSQL in too many ways, and thos
r persistent workloads. Either way,
this is probably a question better asked at the Amazon EC2 forums rather
than PostgreSQL as you'll find more people who know the EC2 interactions
there.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
se for pgaudit to, at least by option, not include DDL
statements that are generated as "sub-parts" of a CREATE EXTENSION? It
should still log the CREATE EXTENSION of course, but not necessarily all
the contents of it, since that's actually defined in the extension itself
already?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
and can migrate the data with
> updated index definitions if it will actually help performance in any way.
> (I'm always looking for ways to tweak the performance for the better any
> chance I get.)
>
>
Hash indexes unfortunately don't support UNIQUE indexes. At least not yet.
So while y
