On 4/2/15 2:18 PM, TonyS wrote:
On Wed, April 1, 2015 5:50 pm, Tom Lane-2 [via PostgreSQL] wrote:
>
>
> TonyS <[hidden email]
> writes:
>
>> The analyze function has crashed again while the overcommit entries
>> were as above. The last bit of the PostgreSQL log shows: MdSmgr:
41934848
>>
On Wed, April 1, 2015 5:50 pm, Tom Lane-2 [via PostgreSQL] wrote:
>
>
> TonyS writes:
>
>> The analyze function has crashed again while the overcommit entries
>> were as above. The last bit of the PostgreSQL log shows: MdSmgr: 41934848
>> total in 14 blocks; 639936 free (0 chunks); 41294912 used
TonyS writes:
> The analyze function has crashed again while the overcommit entries were
> as above. The last bit of the PostgreSQL log shows:
> MdSmgr: 41934848 total in 14 blocks; 639936 free (0 chunks); 41294912 used
> ident parser context: 0 total in 0 blocks; 0 free (0 chunks); 0 used
>
On Wed, April 1, 2015 9:35 am, Kevin Grittner-5 [via PostgreSQL] wrote:
>
>
> TonyS wrote:
>
>
>> The postgresql log has these entries at the crash point:
>> 2015-04-01 06:24:37 EDT LOG: server process (PID 1384) was terminated
>> by signal 9: Killed 2015-04-01 06:24:38 EDT DETAIL: Failed proce
On Wed, 1 Apr 2015 10:47:32 -0700 (MST)
TonyS wrote:
> On Wed, April 1, 2015 12:30 pm, Igor Neyman [via PostgreSQL] wrote:
> >>
> >> TonyS <[hidden email]>
> >> wrote:
> >>
> >>
> >
> > name,current_setting,source autovacuum,off,configuration file
> > synchronous_commit,off,configuration file Tim
On Wed, April 1, 2015 12:30 pm, Igor Neyman [via PostgreSQL] wrote:
>>
>> TonyS <[hidden email]>
>> wrote:
>>
>>
>
> name,current_setting,source autovacuum,off,configuration file
> synchronous_commit,off,configuration file TimeZone,localtime,configuration
> file unix_socket_directories,/var/run/pos
al-ow...@postgresql.org] On Behalf Of FarjadFarid(ChkNet)
Sent: 01 April 2015 17:14
To: 'TonyS'; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Would like to know how analyze works technically
Because your system had crashed. I would check everything from bottom up.
The duration o
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of TonyS
Sent: Wednesday, April 01, 2015 12:15 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Would like to know how analyze works technically
On Wed, April 1, 2015 9:35 am, Kevin
On Wed, April 1, 2015 9:35 am, Kevin Grittner-5 [via PostgreSQL] wrote:
>
>
> TonyS wrote:
>
>
>> The postgresql log has these entries at the crash point:
>> 2015-04-01 06:24:37 EDT LOG: server process (PID 1384) was terminated
>> by signal 9: Killed 2015-04-01 06:24:38 EDT DETAIL: Failed proce
st Regards
Farjad
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of TonyS
Sent: 01 April 2015 14:46
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Would like to know how analyze works technically
On Wed, April 1, 20
essage-
> From: pgsql-general-ow...@postgresql.org
> [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Bill Moran
> Sent: 01 April 2015 13:48
> To: TonyS
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Would like to know how analyze works technically
>
>
&g
On Wed, 1 Apr 2015 06:26:36 -0700 (MST)
TonyS wrote:
> On Wed, April 1, 2015 8:48 am, Bill Moran [via PostgreSQL] wrote:
> >
>
> Running "analyze verbose;" and watching top, the system starts out
> using no swap data and about 4GB of cached memory and about 1GB of
> used memory. A
TonyS wrote:
> The postgresql log has these entries at the crash point:
> 2015-04-01 06:24:37 EDT LOG: server process (PID 1384) was terminated by
> signal 9: Killed
> 2015-04-01 06:24:38 EDT DETAIL: Failed process was running: analyze verbose;
That was almost certainly the action of the OS's
On Wed, April 1, 2015 8:48 am, Bill Moran [via PostgreSQL] wrote:
>
Running "analyze verbose;" and watching top, the system starts out
using no swap data and about 4GB of cached memory and about 1GB of
used memory. As it runs, the amount of used RAM climbs, and
eventually the u
: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Would like to know how analyze works technically
On Wed, 1 Apr 2015 04:33:07 -0700 (MST)
TonyS wrote:
> On Wed, April 1, 2015 12:18 am, Tom Lane-2 [via PostgreSQL] wrote:
> >
> > TonyS writes:
> >
> >> Running "
On Wed, 1 Apr 2015 04:33:07 -0700 (MST)
TonyS wrote:
> On Wed, April 1, 2015 12:18 am, Tom Lane-2 [via PostgreSQL] wrote:
> >
> > TonyS writes:
> >
> >> Running "analyze verbose;" and watching top, the system starts out
> >> using no swap data and about 4GB of cached memory and about 1GB of used
On Wed, April 1, 2015 12:18 am, Tom Lane-2 [via PostgreSQL] wrote:
>
>
> TonyS writes:
>
>> Running "analyze verbose;" and watching top, the system starts out
>> using no swap data and about 4GB of cached memory and about 1GB of used
>> memory. As it runs, the amount of used RAM climbs, and event
TonyS writes:
> Running "analyze verbose;" and watching top, the system starts out using no
> swap data and about 4GB of cached memory and about 1GB of used memory. As it
> runs, the amount of used RAM climbs, and eventually the used swap memory
> increases to 100% and after being at that level fo
I have loaded data for a database conversion I am working on and I have
created the indexes I believe I will need.
My current design uses a schema for each client that will access the
database. I am using schema because there is one set of global tables that I
need to query with the tables within
19 matches
Mail list logo
