2018-03-25 0:41 GMT+01:00 Blair Boadway :
> Thanks for the tip. We are using RHEL 6.9 and definitely up to date on
> glibc (2.12-1.209.el6_9.2). We also have the same versions on a very
> similar system with no segfault.
>
>
>
> My colleague got a better backtrace that shows another extension
>
Hi Blair,
In regards of that debug package i found it here:
http://cbs.centos.org/koji/buildinfo?buildID=20425 , see
http://cbs.centos.org/kojifiles/packages/rh-postgresql96-postgresql/9.6.5/1.el7/x86_64/rh-postgresql96-postgresql-debuginfo-9.6.5-1.el7.x86_64.rpm
However I have very little expe
Thanks for the tip. We are using RHEL 6.9 and definitely up to date on glibc
(2.12-1.209.el6_9.2). We also have the same versions on a very similar system
with no segfault.
My colleague got a better backtrace that shows another extension
Core was generated by `postgres: batch_user_account''.
On Thu, Mar 8, 2018 at 9:40 AM, Blair Boadway wrote:
> Mar 7 14:46:35 pgprod2 kernel:postgres[29351]: segfault at 0 ip
> 00302f32868a sp 7ffcf1547498 error 4 in
> libc-2.12.so[302f20+18a000]
>
> Mar 7 14:46:35 pgprod2 POSTGRES[21262]: [5] user=,db=,app=client= LOG:
> server process (
Following up on this thread, we removed pgaudit from the system to eliminate on
variable (removed from postgres.conf including shared_preload_libraries) but
after a couple of weeks of success we hit the segfault again. Again it
happened while running some DDL (object grants). This time we were
On 03/24/2018 11:03 AM, HORDER Phil wrote:
I'm running Postgres 9.6.1 (I think)
To find out for sure do:
psql> select version();
Phil Horder
Database Mechanic
--
Adrian Klaver
adrian.kla...@aklaver.com
> This was never explained. You are running "process 2" in an entirely
> different session
Yes, two processes are required to get a deadlock.
> If that is true, why don't you commit the updates to table pl and release the
> locks?
It's a long story... but I can't change it at the moment,
Am 23.03.2018 um 23:04 schrieb MOISES ESPINOSA:
I don't know how i could reproduced case insensitive and accent
insensitive.
Maybe you can use lower() for case insensitive or citext for the same
(https://www.postgresql.org/docs/10/static/citext.html) and the
unaccent-extension
for the accen
Hello Phil,
On Fri, 2018-03-23 at 15:42 +, HORDER Phil wrote:
> Rob, thanks for looking.
>
> The "pause" is only to not-do-the-commit yet, so that the child
> process can then try and access the record - I've not left anything
> out.
> This code is my own demo, not a cut from our production
Many thanks Phil for complementary information .
Le sam. 24 mars 2018 à 09:53, HORDER Phil
a écrit :
> Some databases will create a unique index for you when you create a
> primary key.
>
> Oracle will create one, but only if you haven’t already done that.
>
>
>
> Postgres will ALWAYS create a u
Some databases will create a unique index for you when you create a primary key.
Oracle will create one, but only if you haven’t already done that.
Postgres will ALWAYS create a unique index based on the primary key – so you
should never do that as well, or the db will have to maintain two identi
11 matches
Mail list logo
