On Wed, Jan 9, 2019 at 3:52 PM Haroldo Kerry wrote:
> @Justin @Merlin @ Jeff,
> Thanks so much for your time and insights, they improved our understanding
> of the underpinnings of PostgreSQL and allowed us to deal the issues we
> were facing.
> Using parallel query on our PG 9.6 improved a lot
@Justin @Merlin @ Jeff,
Thanks so much for your time and insights, they improved our understanding
of the underpinnings of PostgreSQL and allowed us to deal the issues we
were facing.
Using parallel query on our PG 9.6 improved a lot the query performance -
it turns out that a lot of our real
Oups wrong copy and paste. I did run your query with equal instead of in but it
resulted in the same plan
From: David Rowley
Sent: 09 January 2019 17:41:24
To: Abadie Lana
Cc: Justin Pryzby; pgsql-performance@lists.postgresql.org
Subject: Re: select query does
On Thu, 10 Jan 2019 at 01:55, Abadie Lana wrote:
> The other query suggested by D.Rowley has the same issue : still swap
> activity is higher.
> explain analyze select 'BUIL-B36-VA-RT-RT1:CL0001-2-ABW',
> c.smpl_time,c.nanosecs,c.float_val,c.num_val,c.str_val,c.datatype,c.array_val
> from
But in both of the machines I have the same os and I used the same
repository - postgresql rpm repository. The only difference is that in
machine 2 I also installed all pg 9.6 packages. Even When I try to use
/usr/pgsql-9.2/bin/psql the psql still tries to access the
/var/run/run/postgresql dir as
On Wed, Jan 9, 2019 at 10:09 AM Mariel Cherkassky <
mariel.cherkas...@gmail.com> wrote:
> Hey Tom,
> I'm aware of how I can solve it. I wanted to understand why after
> installing the pg 9.6 packages suddenly psql tries to access the socket on
> /var/run/postgresql. Does the libpq default unix
On Wed, Jan 9, 2019 at 3:35 AM Mariel Cherkassky <
mariel.cherkas...@gmail.com> wrote:
>
> Now, In machine 1 when I run psql I get the prompt password but in machine
> 2 I keep getting the next error :
>
> psql: could not connect to server: No such file or directory
> Is the server
Hey Tom,
I'm aware of how I can solve it. I wanted to understand why after
installing the pg 9.6 packages suddenly psql tries to access the socket on
/var/run/postgresql. Does the libpq default unix socket is changed between
those two versions ? (9.6,9.2)
בתאריך יום ד׳, 9 בינו׳ 2019 ב-16:55 מאת
Mariel Cherkassky writes:
> I'm trying to understand some issues that I'm having with the unix_socket
> settings and pgsql.
> I have 2 machines with pg v9.2.5 with the same next settings :
> #listen_addresses = 'localhost'
> #unix_socket_directory = ''
This will result in the server creating the
-Original Message-
From: Justin Pryzby
Sent: 08 January 2019 09:15
To: Abadie Lana
Cc: David Rowley ;
pgsql-performance@lists.postgresql.org
Subject: Re: select query does not pick up the right index
On Mon, Jan 07, 2019 at 04:09:50PM +, Abadie Lana wrote:
> "channel_pkey"
>
> I installed on machine 2 the next packages and not what I mentioned on my
> last comment :
>
---> Package postgresql96.x86_64 0:9.6.10-1PGDG.rhel6 will be installed
---> Package postgresql96-contrib.x86_64 0:9.6.10-1PGDG.rhel6 will be
installed
---> Package postgresql96-libs.x86_64
Hi,
I'm trying to understand some issues that I'm having with the unix_socket
settings and pgsql.
I have 2 machines with pg v9.2.5 with the same next settings :
#listen_addresses = 'localhost'
#unix_socket_directory = ''
in both of the machines I run netstat to check on what socket the postgres
12 matches
Mail list logo