Oh, here is more context about this issue:
http://www.postgresql.org/message-id/201208171307.16342.and...@2ndquadrant.com
-- Valentin
On Wed, Aug 28, 2013 at 1:28 AM, Valentine Gogichashvili
wrote:
> Hello Andreas,
>
> it is more then a year now, that I have not returned to that topi
Hello
This is a well documented feature of Hot-Standby Replication.
see:
http://www.postgresql.org/docs/9.2/static/runtime-config-replication.html#RUNTIME-CONFIG-REPLICATION-STANDBY
Regards,
-- Valentin
ვალენტინ გოგიჩაშვილი
Valentine Gogichashvili
On Wed, Aug 28, 2013 at 2:30 AM, wrote
lly read-only sprocs like
now() :)
Regards,
Valentine Gogichashvili
Hello John,
>> we see up to 10x performance increase with bigger shared_buffers in case
>> of this database. Main database entities are about 20GB in size and we see
>> that performance drops considerably when running with smaller
>> shared_buffers smaller then that.
>>
>>
> do you adjust effecti
3039 total
With best regards,
-- Valentine Gogichashvili
On Thu, Aug 16, 2012 at 4:53 PM, Valentine Gogichashvili
wrote:
> Hello Andreas,
>
> here is the process, that now actually is not using CPU at all and the
> shared_buffers are set to 2GB:
>
> 50978 postgres 20 0 2288
like to see?
Regards,
-- Valentin
On Wed, Aug 15, 2012 at 4:09 PM, Andres Freund wrote:
> Hi,
>
> On Wednesday, August 15, 2012 12:10:42 PM val...@gmail.com wrote:
> > The following bug has been logged on the website:
> >
> > Bug reference: 7494
> &
Hallo John,
On Wed, Aug 15, 2012 at 3:40 PM, John R Pierce wrote:
> On 08/15/12 6:36 AM, Bruce Momjian wrote:
>
>> We warn against making shared buffers > 8GB, and this is perhaps another
>> good reason.
>>
>
> I generally keep it at no more than 2gb as I've never found any
> performance improve
Hallo Andreas,
> Could you try to get a profile of that 100% cpu time?
>
>
Yes I will try to do it.
-- Valentine
.
What I can do, is to switch streaming replication on one of the machines
off, and wait :(
Would it be possible to somehow generate a workload, that would lead to
this a problem?
With best regards,
-- Valentine Gogichashvili
On Thu, Jun 7, 2012 at 6:49 PM, Andres Freund wrote:
> On Thursday, J
>
> This email thread from 2010 has a similar problem:
>http://archives.postgresql.org/pgsql-hackers/2010-10/msg00772.php
> What is limiting a fix for this is the breaking of existing behavior,
> and the breaking of indexes used during pg_upgrade.
> I have added your email to the existing T
,
-- Valentine Gogichashvili
On Wed, May 23, 2012 at 10:51 PM, Valentine Gogichashvili
wrote:
> But no subtransactions with writes (plpgsql + EXCEPTION also counts if does
>> DML)?
>>
>>
> On the master, yes. Practically all the stored procedures there are
> catching exc
Hello Andres,
Do you have both, longrunning transactions and transactions with many
> subtransactions?
>
> Yes long running plane SQL queries as well as many short SQL queries
running one after another in one long spanning transaction (we are working
on eliminating this kind of behavior, but it is
>
> > 2012-05-22 21:20:27.868 CEST,,,23804,,4fbbe69e.5cfc,130,,2012-05-22
> > 21:18:54 CEST,1/0,0,FATAL,XX000,"out-of-order XID insertion in
> > KnownAssignedXids","xlog redo running xacts: nextXid 3674728633
> > latestCompletedXid 3674728632 oldestRunningXid 3674726497; 4 xacts:
> > 367472704
ST,,,21080,,4fbc2a84.5258,36,,2012-05-23 02:08:36
CEST,1/0,0,FATAL,XX000,"out-of-order XID insertion in
KnownAssignedXids","xlog redo running xacts: nextXid 3675658265
latestCompletedXid 3675658264 oldestRunningXid 3675654963; 4 xacts:
3675655620 3675655621 3675655814 3675654963&quo
ECT without INTO in plpgsql,
there also would be no PERFORM command in plpgsql...
Best regards,
-- Valentine Gogichashvili
>
>
> I suppose you could argue that selecting a value and implicitly throwing
> it away is confusing to novices, but on the other hand I've seen a whole
> lot of novices confused by the need to write PERFORM instead of SELECT.
> I think it wouldn't be an unreasonable thing to just interpret a SELE
>
>
> ssl = false
> shared_buffers = 900MB # min 128kB
> work_mem = 100MB# min 64kB
> maintenance_work_mem = 524MB# min 1MB
> fsync = off # turns forced synchronization on
> or off
> synchronous_commit = off
migration, or in 8.4
to use the
rec.var := ( SELECT ROW(..) .. );
syntax.
With my best regards,
-- Valentine Gogichashvili
On Wed, Sep 8, 2010 at 5:42 PM, Tom Lane wrote:
> Valentine Gogichashvili writes:
> > CREATE TYPE ta AS (a1 integer, a2 text);
> > CREATE TYPE tb AS (b1
SELECT 100, 'a' INTO b.b2; -- ok in 9.0 but fails in 8.4 [ERROR: cannot
assign non-composite value to a row variable]
RAISE INFO 'b is %', b;
END
$DOIT$;
select public.foo();
ROLLBACK;
Best ragards,
-- Valentine Gogichashvili
On Sun, Sep 5, 2010 at 5:27 PM, Tom Lane
The following bug has been logged online:
Bug reference: 5644
Logged by: Valentine Gogichashvili
Email address: val...@gmail.com
PostgreSQL version: 9.0RC1
Operating system: linux
Description:Selecting ROW() in variable with 9.0 not compatible with
8.4
Details
Hi,
Actually full_page_write being turned off on the master is probably a
problem.
-- Valentine
On Thu, Aug 12, 2010 at 9:43 AM, Fujii Masao wrote:
> On Thu, Aug 12, 2010 at 4:18 PM, Simon Riggs
> wrote:
> > The safest approach is to
> >
> > 1. run pg_start_backup() on master, remember LSN
>
The following bug has been logged online:
Bug reference: 5574
Logged by: Valentine Gogichashvili
Email address: val...@gmail.com
PostgreSQL version: 9.0beta3
Operating system: RedHat Linux (2.4.21-53.ELsmp)
Description:PANIC on hot-standby: heap_update_redo
Details
The following bug has been logged online:
Bug reference: 5465
Logged by: Valentine Gogichashvili
Email address: val...@gmail.com
PostgreSQL version: 8.2.1
Operating system: Red Hat 3.4.6-3 (kernel 2.6.9-42.0.3.ELsmp)
Description:dblink TCP connection hangs blocking
ons working with one dimension integer arrays,
it could return a really empty array with construct_empty_array() if the num
is 0 instead of doing the resize as it is done now.
With best regards,
-- Valentine Gogichashvili
On Tue, Jan 13, 2009 at 7:22 PM, Tom Lane wrote:
> "Valentine Gogi
The following bug has been logged online:
Bug reference: 4613
Logged by: Valentine Gogichashvili
Email address: val...@gmail.com
PostgreSQL version: 8.3.1
Operating system: Debian Linux (kernel 2.6.8)
Description:intarray_del_elem returns an invalid empty array (for
The following bug has been logged online:
Bug reference: 4319
Logged by: Valentine Gogichashvili
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: SuSE Linux (kernel 2.6.13-15.11-default)
Description:lower()/upper() does not know about
The following bug has been logged online:
Bug reference: 3942
Logged by: Valentine Gogichashvili
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Linux 2.6.8 SMP
Description:Related to BUG #2568 and BUG #2859: VACUUM process hangs
and does
27 matches
Mail list logo
