g that stands out is that in your original
> post you had:
>
> -p 5432
>
> and above you have:
>
> -p 5433
>
> Not sure if that makes a difference.
>
> The only suggestion I have at the moment is to move -c from the end of the
> line to somewhere earlier
ight never have seen your $silly-dash since possibly
your shell or terminal driver swallowed it.
>
> Thanks for pointing that out. I will redo my upgrade.
>
> -r -v -k -c --- good flags no utf8
> -r -v -k –c --- bad flags....
>
>
>
>
> -Original Message-
>
kunwar singh writes:
> Hi Listers,
> Anyone here use such a tool for Postgres? Any recommendations?
>
> Say I have 150 queries in Postgres 11 and I want to upgrade to Postgres 15. I
> want to run explain analyze for 150 in both versions for comparative
> analysis.
>
> I am looking for the easie
That error or a very similar one was fixed in a recent point release.
HTH
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consult...@comcast.net
llocation is. I cant see
> anything in the docs which tells me how to interpret the integer.
>
> Any clarification welcome.
>
> Regards
> Bob
>
>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consult...@comcast.net
Jerry Sievers writes:
> Bob Jolliffe writes:
>
>> Excuse me if this is a silly question. I am trying to fiddle with
>> shared_buffers setting on postgresql 10.6 on ubuntu 18.04 server.
>>
>> I have this at bottom of my config file:
>> shared_buffers = 1G
number of files for the table
> has grown, the system is spending more and more time seeking around
> the disk to touch all those files for some reason?
>
> Does anyone who understands the details of postgresql's interaction
> with the file system have an explanation for why all those files
> which are full are being touched constantly?
>
>
>
>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consult...@comcast.net
