Re: [GENERAL] Bug in postgres 9.6.2?

If I can provide a pg_dump backup with a db where I can reproduce the error and then also my postgresql.conf along with the query, would that be what you need for a test case? Thanks, Greig -- View this message in context:

Re: [GENERAL] Bug in postgres 9.6.2?

I do still have the 9.6.2 instance. Here is the explain analyze results from the 9.6.2 instance: Aggregate (cost=764612.56..764612.57 rows=1 width=8) (actual time=695.166..695.166 rows=1 loops=1) CTE test -> Nested Loop (cost=3345.90..757594.63 rows=311908 width=4) (actual

[GENERAL] Bug in postgres 9.6.2?

So, I have this query with nothing non-deterministic in it, yet I can run it multiple times and get different results in postgres 9.6.2: with test as ( select g.id2 from staging a join dim_1 e on e.id1 = a.id1 and a.created_at >= e.effective_at and a.created_at < e.expired_at join dim_2 g on

Re: [GENERAL] Weirdness with "not in" query

Wow. That is exactly it. Thank you. I really would not have expected there to be NULLs in that field. Geez. -- View this message in context: http://www.postgresql-archive.org/Weirdness-with-not-in-query-tp5965573p5965576.html Sent from the PostgreSQL - general mailing list archive at

[GENERAL] Weirdness with "not in" query

So, I'm using postgres version 9.6.3 on a mac and the results to this series of queries seems very strange to me: db# select count(*) from table1 where id in (1706302,1772130,1745499,1704077); count --- 4 (1 row) db# select count(*) from table2 where table1_id in

Re: [GENERAL] Query with large in clauses uses a lot of memory

Wow. Thanks for the prompt answer. As a follow-up I was wondering if maybe there would be a way to tell it to NOT try to plan/execute the query (and instead throw an error) if the memory usage exceeded X. Thanks again. Greig -- View this message in context:

[GENERAL] Query with large in clauses uses a lot of memory

I had an issue today where the OOM killer terminated one of my postgres processes. On my server I have 8 GB of RAM, shared_memory is 1 GB and work_memory is 24MB. I have connection pooling which limits us to 25 connections. Even if I'm maxed out there, I'm still only using 1.6 MB of RAM of my

Re: [GENERAL] GSS Authentication

Bryan, one thing I did have to do on the Linux side was to set dns_lookup_kdc = true in my krb5.conf file in the libdefaults section. Hope that helps. Greig - Original Message - From: greigw...@comcast.net To: Bryan Montgomery mo...@english.net, sfr...@snowman.net Cc: pgsql-general

Re: [GENERAL] GSS Authentication

2008 - Original Message - From: Stephen Frost sfr...@snowman.net To: greigw...@comcast.net Cc: Bryan Montgomery mo...@english.net, pgsql-general pgsql-general@postgresql.org Sent: Wednesday, June 16, 2010 11:32:05 AM GMT -05:00 US/Canada Eastern Subject: Re: [GENERAL] GSS

Re: [GENERAL] GSS Authentication

One interesting thing I just came across. I had another user try to connect to my DB using the GSS authentication and it failed. I checked everything out on the client side and it seemed to be OK, so I was puzzled. So then I had another user try and it worked just fine for him. That's weird,

Re: [GENERAL] GSS Authentication

OK. So, to get it to use a different encryption type, I'm thinking I'd have to specify that when I create the keytab (and then uncheck the Use DES option on the account setup in Windows). So, when I created my keytab, I used a command like this on the AD side: ktpass -princ

Re: [GENERAL] GSS Authentication

OMG!!! I finally got it working. Problem was that on the windows side on the service account within the account options, we needed to check Use DES encryption types for this account. I had that changed on the AD side and that fixed the whole problem. Bryan, if you're still trying to get

Re: [GENERAL] GSS Authentication

As suggested below, I just tried this: kinit -S POSTGRES/host.domain.com user (where user is my account name in AD). That then asked for my password and when I entered it, it seemed to work. And now klist shows that I have a ticket. Doing it this way though, the keytab file doesn't seem to

Re: [GENERAL] GSS Authentication

OK. I tried what you suggested. I pasted the whole sequence of commands and the results below. As you can see, the connection to postgres still failed, but it looks like it actually acquired the ticket (I think). What do you make of that? Thanks again for the help. Greig [u...@client ~]$

Re: [GENERAL] GSS Authentication

I just notice that in your message you had more text further down (regarding the DES encryption). I didn't see that at first. So, I did klist -e as you suggested and I got this: Ticket cache: FILE:/tmp/krb5cc_502 Default principal: u...@domain.com Valid starting Expires Service principal

Re: [GENERAL] GSS Authentication

Thanks for the help. In response to your questions, I did make sure the service name was right. klist -k on the keytab file gives: KVNO Principal --    3 POSTGRES/hostname.domain@domain.com I

Re: [GENERAL] GSS Authentication

One other thing possibly worth noting I tried to connect to the Postgres DB using pgAdmin III and it gives a very similar error to the test perl program that I wrote: Error connecting to the server: FATAL: accepting GSS security context failed DETAIL: Miscellaneous failure: Unknown

[GENERAL] GSS Authentication

I'm trying to get my PostgreSQL server on Linux configured so that I can connect from a Windows client using GSS Authentication against Active Directory. I found some helpful references on how to do this, but I'm still coming up short. To summarize what I've done so far by way of configuration: