On Wed, 2013-11-20 at 01:08 +0200, Oskari Saarenmaa wrote:
> Agreed. Attached an updated patch, or you can grab it from
> https://github.com/saaros/postgres/compare/extra-version
Committed.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
On 12 Dec 2013 04:20, "Álvaro Hernández Tortosa" wrote:
> Thanks, Greg. I've been going through those threads, they are
quite interesting. I didn't find an answer, though, about my question: why
parsing the postgresql.conf (and for instance preserving the comments while
writing it back) i
PGCon 2014 will be on 20-24 May 2014 at University of Ottawa.
* 20-21 (Tue-Wed) tutorials
* 22-23 (Thu-Fri) talks - the main part of the conference
* 24 (Sat) The Unconference (very popular in 2013, the first year)
See http://www.pgcon.org/2014/
We are now accepting proposals for the main part o
On Dec 12, 2013, at 6:24 PM, Andres Freund wrote:
> Is it really a regular pattern like hourly? What's your
> checkpoint_segments?
No, it's not a pattern like that; that's an approximation. Sometimes, they
come in clusters, sometimes, 2-3 hours past without one. They don't happen
exclusively
On Dec 12, 2013, at 6:41 PM, Andres Freund wrote:
> Christophe: are there any "unusual" ERROR messages preceding the crash,
> possibly some minutes before?
Interestingly, each spinlock PANIC is *followed*, about one minute later (+/-
five seconds) by a "canceling statement due to statement tim
On Thu, Dec 12, 2013 at 7:35 PM, Christophe Pettus wrote:
> There are a *lot* of "canceling statement due to statement timeout" messages,
> which is interesting, because:
>
> postgres=# show statement_timeout;
> statement_timeout
> ---
> 0
> (1 row)
Couldn't that just be the ap
On Fri, Dec 13, 2013 at 12:03 PM, Peter Eisentraut wrote:
> On Wed, 2013-11-20 at 01:08 +0200, Oskari Saarenmaa wrote:
>> Agreed. Attached an updated patch, or you can grab it from
>> https://github.com/saaros/postgres/compare/extra-version
>
> Committed.
Thanks.
--
Michael
--
Sent via pgsql-
On Dec 12, 2013, at 7:40 PM, Peter Geoghegan wrote:
> Couldn't that just be the app setting it locally?
Yes, that's what is happening there (I had to check with the client's
developers). It's possible that the one-minute repeat is due to the
application reissuing the query, rather than specif
On 04 December 2013, Sawada Masahiko Wrote
> I attached the patch which have modified based on Robert suggestion,
> and fixed typo.
I have reviewed the modified patch and I have some comments..
1. Patch need to be rebased (failed applying on head)
2. crc field should be at end in ControlFileDa
On Fri, Dec 13, 2013 at 1:51 PM, Dilip kumar wrote:
> On 04 December 2013, Sawada Masahiko Wrote
>
>
>> I attached the patch which have modified based on Robert suggestion,
>> and fixed typo.
>
> I have reviewed the modified patch and I have some comments..
>
> 1. Patch need to be rebased (failed
On 13/12/13 04:11, Greg Stark wrote:
On 12 Dec 2013 04:20, "Álvaro Hernández Tortosa" mailto:a...@nosys.es>> wrote:
> Thanks, Greg. I've been going through those threads, they are
quite interesting. I didn't find an answer, though, about my question:
why parsing the postgresql.conf (
On Thu, Dec 12, 2013 at 12:47 PM, Dev Kumkar wrote:
> + hackers
>
>
>
> On Thu, Dec 12, 2013 at 12:34 PM, Dev Kumkar wrote:
>
>> On Wed, Dec 11, 2013 at 9:47 PM, Dev Kumkar wrote:
>>
>>> Actually for searches lower will work.
>>> But the other important aspect is 'inserts' which would result 2 row
101 - 112 of 112 matches
Mail list logo
