Re: [BUGS] Prepared Statement Name Truncation

Phil Sorber writes: > I think making this a warning now would be a bit more forceful way to > let people know that this is a bad idea and this is a case where maybe > they need to work around postgres' lack of conformance to the spec. It > would most likely be caught sooner as well by DBA's. Then

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

Andres Freund writes: > On 2012-11-18 14:07:37 -0500, Tom Lane wrote: >> Anyway, even if Linux for some reason doesn't reject negative values, >> I think we need to limit the GUC's range so we don't try to use them. >> Maybe you'd get sane behavior and maybe you wouldn't. I notice that >> the Sin

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

Marc Balmer writes: > Am 18.11.2012 um 19:36 schrieb Peter Geoghegan : >> Right. sizeof(int) is very probably 4 on all platforms that we >> support. I see no problem with the proposal. > Have you cross-checked this on a 64bit platform vs. a 32 bit platform? > e.g. on Linux i386 vs. Linux amd64?

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

On 2012-11-18 14:07:37 -0500, Tom Lane wrote: > Andres Freund writes: > > On 2012-11-18 13:18:42 -0500, Tom Lane wrote: > >> Well, we have two reports of people trying such values (assuming that > >> #7545 actually is the same thing), and it didn't work for either of > >> them. I don't think it's

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

Andres Freund writes: > On 2012-11-18 13:18:42 -0500, Tom Lane wrote: >> Well, we have two reports of people trying such values (assuming that >> #7545 actually is the same thing), and it didn't work for either of >> them. I don't think it's a problem to restrict the value to something >> that wi

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

On 18 November 2012 18:42, Marc Balmer wrote: > Have you cross-checked this on a 64bit platform vs. a 32 bit platform? > e.g. on Linux i386 vs. Linux amd64? Well, strictly speaking sizeof(int) is dictated by both the compiler and CPU architecture in question. I believe that all current Unix-like

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

On 2012-11-18 13:18:42 -0500, Tom Lane wrote: > Andres Freund writes: > > On 2012-11-18 12:44:55 -0500, Tom Lane wrote: > >> I'm inclined to propose limiting both of these to the equivalent of 15 > >> days. Alternatively we could try to rejigger things to prevent asking > >> WaitLatch to wait for

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

Am 18.11.2012 um 19:36 schrieb Peter Geoghegan : > On 18 November 2012 18:18, Tom Lane wrote: >> Well, we have two reports of people trying such values (assuming that >> #7545 actually is the same thing), and it didn't work for either of >> them. I don't think it's a problem to restrict the val

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

On 18 November 2012 18:18, Tom Lane wrote: > Well, we have two reports of people trying such values (assuming that > #7545 actually is the same thing), and it didn't work for either of > them. I don't think it's a problem to restrict the value to something > that will work rather than fail. Righ

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

2012/11/18 Tom Lane > Andres Freund writes: > > On 2012-11-18 12:44:55 -0500, Tom Lane wrote: > >> I'm inclined to propose limiting both of these to the equivalent of 15 > >> days. Alternatively we could try to rejigger things to prevent asking > >> WaitLatch to wait for more than 2^31 msec, bu

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

Andres Freund writes: > On 2012-11-18 12:44:55 -0500, Tom Lane wrote: >> I'm inclined to propose limiting both of these to the equivalent of 15 >> days. Alternatively we could try to rejigger things to prevent asking >> WaitLatch to wait for more than 2^31 msec, but it's not real clear to >> me t

Re: [BUGS] Prepared Statement Name Truncation

On Sun, Nov 18, 2012 at 2:33 AM, Tom Lane wrote: > Phil Sorber writes: >> An install of ours was having an issue with log files filling up the >> disk rather quickly. After looking into it, the log was filling up >> with NOTICE's caused by an ORM that was using a very long identifier >> as a name

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

On 2012-11-18 12:44:55 -0500, Tom Lane wrote: > Igor writes: > > 2012/11/18 Tom Lane > >> I was just about to ask what you have log_rotation_age set to ... > > > Was: > > log_rotation_age = 30d > > That's the problem then. Internally that gets converted to > milliseconds, which'll overflow at 24

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

2012/11/18 Tom Lane > Igor writes: > > 2012/11/18 Tom Lane > >> I was just about to ask what you have log_rotation_age set to ... > > > Was: > > log_rotation_age = 30d > > That's the problem then. Internally that gets converted to > milliseconds, which'll overflow at 24-something days. Use a

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

2012/11/18 Andres Freund > On 2012-11-18 12:29:29 -0500, Tom Lane wrote: > > Igor writes: > > > I feel :) that the problem is in "logging_collector" setting - I used > this > > > feature. But now I comments this setting in config. And will watching > .. > > > > I was just about to ask what you h

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

Peter Geoghegan writes: > I haven't looked at this in detail, but are you sure that this isn't > the bug that was fixed by commit > e81e8f9342b037246b284bad15e42e21b1929301 ? The "invalid argument" > poll() error is too generic to be sure what is really at fault, but > this doesn't need to be a FA

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

On 2012-11-18 17:36:40 +, Peter Geoghegan wrote: > On 18 November 2012 17:12, Andres Freund wrote: > > Ok, this is already helpful. Do you have anything the log that shows > > what process pid 95528 is? Could you grep for it? > > I haven't looked at this in detail, but are you sure that this

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

Igor writes: > 2012/11/18 Tom Lane >> I was just about to ask what you have log_rotation_age set to ... > Was: > log_rotation_age = 30d That's the problem then. Internally that gets converted to milliseconds, which'll overflow at 24-something days. Use a smaller value. So the actual bug here

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

On 2012-11-18 12:29:29 -0500, Tom Lane wrote: > Igor writes: > > I feel :) that the problem is in "logging_collector" setting - I used this > > feature. But now I comments this setting in config. And will watching .. > > I was just about to ask what you have log_rotation_age set to ... According

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

On 18 November 2012 17:12, Andres Freund wrote: > Ok, this is already helpful. Do you have anything the log that shows > what process pid 95528 is? Could you grep for it? I haven't looked at this in detail, but are you sure that this isn't the bug that was fixed by commit e81e8f9342b037246b284bad

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

2012/11/18 Tom Lane > Igor writes: > > I feel :) that the problem is in "logging_collector" setting - I used > this > > feature. But now I comments this setting in config. And will watching .. > > I was just about to ask what you have log_rotation_age set to ... > > Was: log_rotation_age = 30d

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

On 2012-11-18 19:22:04 +0200, Igor wrote: > 2012/11/18 Andres Freund > > > On 2012-11-18 18:53:13 +0200, Igor wrote: > > > .. > > > > > > > Could you give a bit more context about when exactly that error is > > > > happening? > > > > It would also be helpful if you could set log_error_verbosity =

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

Igor writes: > I feel :) that the problem is in "logging_collector" setting - I used this > feature. But now I comments this setting in config. And will watching .. I was just about to ask what you have log_rotation_age set to ... regards, tom lane -- Sent via pgsql-bu

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

2012/11/18 Andres Freund > On 2012-11-18 18:53:13 +0200, Igor wrote: > > .. > > > > > Could you give a bit more context about when exactly that error is > > > happening? > > > It would also be helpful if you could set log_error_verbosity = > > > 'verbose'; in the config file and report back with

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

On 2012-11-18 18:53:13 +0200, Igor wrote: > .. > > > Could you give a bit more context about when exactly that error is > > happening? > > It would also be helpful if you could set log_error_verbosity = > > 'verbose'; in the config file and report back with the complete error > > message, includin

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

And for my previous letter: I feel :) that the problem is in "logging_collector" setting - I used this feature. But now I comments this setting in config. And will watching .. -- Regards System and web developer.

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

.. > Could you give a bit more context about when exactly that error is > happening? > It would also be helpful if you could set log_error_verbosity = > 'verbose'; in the config file and report back with the complete error > message, including line numbers. > > I try to restart DB and seems get t

Re: [BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

On 2012-11-17 21:00:36 +, igorya.inscrip...@gmail.com wrote: > The following bug has been logged on the website: > > Bug reference: 7670 > Logged by: Igor > Email address: igorya.inscrip...@gmail.com > PostgreSQL version: 9.2.1 > Operating system: FreeBSD 9.0 > Description:

Re: [BUGS] BUG #7667: Segmentation fault

I can confirm that REL9_2_STABLE works fine. Thanks for quick help. Regards/Pozdrawiam Jacek Domagalski -Original Message- From: Euler Taveira [mailto:eu...@timbira.com] Sent: Saturday, November 17, 2012 6:56 PM To: Jacek Domagalski Cc: PostgreSQL Bugs Subject: Re: [BUGS] BUG #7667:

[BUGS] BUG #7670: BUG #7545: Unresponsive server with error log reporting: "poll() failed: Invalid argument"

The following bug has been logged on the website: Bug reference: 7670 Logged by: Igor Email address: igorya.inscrip...@gmail.com PostgreSQL version: 9.2.1 Operating system: FreeBSD 9.0 Description: The same a BUG as 7545. Pgsql compiled from FreeBSD ports with option

Re: [GENERAL] [BUGS] Prepared Statement Name Truncation

On Nov 18, 2012, at 2:24, Tom Lane wrote: > "Greg Sabino Mullane" writes: >>> If it's a postgres bug, what is the fix? Make the identifier max size >>> longer? > >> I'd also be in favor of this, in addition to upgrading from a NOTICE. > > On the whole I'm not too excited about changing this. >