Re: The best way to solve a problem

2020-02-04 Thread Nikolai Lusan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hey, On Tue, 2020-02-04 at 18:14 -0700, David G. Johnston wrote: > On Tue, Feb 4, 2020 at 5:36 PM Nikolai Lusan wrote: > > > I > > am a member of a small sporting association that I am doing some > > technical > > stuff for, part of which is desig

Re: The best way to solve a problem

2020-02-04 Thread David G. Johnston
On Tue, Feb 4, 2020 at 5:36 PM Nikolai Lusan wrote: > I > am a member of a small sporting association that I am doing some technical > stuff for, part of which is designing and implementing a DB for membership > and scoring records. > [...] The rest of that planning seems like a significant case

The best way to solve a problem

2020-02-04 Thread Nikolai Lusan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Greeting database brains, Although I started my career with a short lived role as a database administrator, and over the years have created a few small databases of my own, I normally do most of my database things on DB's that have been created by o

Re: Restrict connection from pgadmin.

2020-02-04 Thread raf
Tom Lane wrote: > Pawan Sharma writes: > > Yes I will show the pgadmin in stat_activity but how can block that.. > > I think I need to create a job to terminate the pgadmin connections and > > schedule it for every 5 min and so that I will check any new connections > > from pgadmin. > > I thin

Re: Postgres Crashing

2020-02-04 Thread Doug Roberts
Seems to be working fine now that I've upgraded to 12.1. I'll keep an eye out for 12.2. However, we are not using a before row update trigger. We are using an after insert trigger on the containers table though. Thanks, Doug On Tue, Feb 4, 2020 at 2:34 PM Tom Lane wrote: > Doug Roberts writes

Better documentation for schema changes in logical replication

2020-02-04 Thread Mike Lissner
Hi all, I've been using logical replication for about a year now, and I wonder if there's any sense that it needs better documentation of schema changes. My experience is that there's almost no documentation and that there are lots of opportunities to really screw things up. It seems like startin

Re: Postgres Crashing

2020-02-04 Thread Tom Lane
Doug Roberts writes: > Hopefully the following stack trace is more helpful. > Exception thrown at 0x000140446403 in postgres.exe: 0xC005: Access > violation reading location 0xFFF8. occurred >> postgres.exe!pfree(void * pointer) Line 1033 C > postgres.exe!tts_buffer_heap_cl

Re: Postgres Crashing

2020-02-04 Thread Doug Roberts
Hello, Hopefully the following stack trace is more helpful. Exception thrown at 0x000140446403 in postgres.exe: 0xC005: Access violation reading location 0xFFF8. occurred > postgres.exe!pfree(void * pointer) Line 1033 C postgres.exe!tts_buffer_heap_clear(TupleTableSlot * sl

RE: Add column with default value in big table - splitting of updates can help?

2020-02-04 Thread Kevin Brannen
>From: Durumdara > >a.) >PG version is mainly 9.6, but some of the servers are 10.x or 11.x. >b.) >We have semi-automatic tool which get the a new modifications on databases, >and execute them at once by database. >So one SQL script by one database, under one transaction - whole or nothing. >If

Re: Postgres Crashing

2020-02-04 Thread Adrian Klaver
On 2/4/20 6:20 AM, Doug Roberts wrote: So how did containers_reset_recirc() come to clash with containers_add_update()? They are clashing because another portion of our system is running and updating containers. The reset recirc function was run at the same time to see how our system and the

Re: Postgres Crashing

2020-02-04 Thread Doug Roberts
Sure. Ok then. On Tue, Feb 4, 2020 at 11:18 AM Adrian Klaver wrote: > On 2/4/20 8:06 AM, Doug Roberts wrote: > > Hello, > > > > Here is a stacktrace of what happened before and after the crash. > > Actually the below is the Postgres log. Per Tom's previous post the > procedure to get a stack tra

Re: Postgres Crashing

2020-02-04 Thread Adrian Klaver
On 2/4/20 8:06 AM, Doug Roberts wrote: Hello, Here is a stacktrace of what happenedĀ before and after the crash. Actually the below is the Postgres log. Per Tom's previous post the procedure to get a stack trace can be found here: https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_

Re: Postgres Crashing

2020-02-04 Thread Doug Roberts
Hello, Here is a stacktrace of what happened before and after the crash. Thanks, Doug 2020-02-04 10:26:16.841 EST [20788] [0] LOG: 0: server process (PID 12168) was terminated by exception 0xC005 2020-02-04 10:26:16.841 EST [20788] [0] DETAIL: Failed process was running: select CONTAI

Re: Postgres Crashing

2020-02-04 Thread Doug Roberts
> So how did containers_reset_recirc() come to clash with > containers_add_update()? They are clashing because another portion of our system is running and updating containers. The reset recirc function was run at the same time to see how our system and the database would handle it. The recirc st

Re: Should I reinstall over current installation?

2020-02-04 Thread Moreno Andreo
Il 04/02/2020 00:16, Chris Charley ha scritto: I tried items you suggested (1-5), but could find no helpful info. Thanks for your help and going the extra mile! Hope I'm in time to try