Unix Technical Forum

Re: [BUGS] BUG #1466: #maintenace_work_mem = 16384

This is a discussion on Re: [BUGS] BUG #1466: #maintenace_work_mem = 16384 within the Pgsql Patches forums, part of the PostgreSQL category; --> Actually, I'd like it considered for 8.0.X as well. Right now if yuo change the config file in a ...


Go Back   Unix Technical Forum > Database Server Software > PostgreSQL > Pgsql Patches

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 04-18-2008, 12:06 AM
Magnus Hagander
 
Posts: n/a
Default Re: [BUGS] BUG #1466: #maintenace_work_mem = 16384

Actually, I'd like it considered for 8.0.X as well. Right now if yuo
change the config file in a way that it won't load, you get no error
message. Which is cearly not very good. I'll certainly accept if you
think it's not safe enough for 8.0.x, but please consider it.

//Magnus


>-----Original Message-----
>From: Bruce Momjian [mailtogman@candle.pha.pa.us]
>Sent: den 27 februari 2005 02:04
>To: Magnus Hagander
>Cc: Tom Lane; PostgreSQL-patches; Andreas Pflug
>Subject: Re: [PATCHES] [BUGS] BUG #1466: #maintenace_work_mem = 16384
>
>
>
>Patch applied. Thanks.
>
>I assume this is not for 8.0.X.
>
>---------------------------------------------------------------
>------------
>
>
>Magnus Hagander wrote:
>> >>> The proposed test on Redirect_stderr looks pretty fishy

>too; for one
>> >>> thing it will almost certainly not be the right thing
>> >inside the stderr
>> >>> logger subprocess itself.
>> >
>> >> Could you explain further what the issue is there?
>> >
>> >Inside the logger subprocess, Redirect_stderr is guaranteed

>true (since
>> >it'll be inherited from the postmaster) and therefore the proposed
>> >change ensures that anything the logger might want to complain about
>> >goes to the original stderr, ie, into the bit bucket rather than
>> >someplace useful. Perhaps something like
>> >
>> > if ((!Redirect_stderr || am_syslogger) && pgwin32_is_service())
>> >
>> >would be reasonable.

>>
>> <snip lots of others>
>>
>> Here is an updated patch, that should take care of this.

>Tested that it
>> solves the problem reported.
>>
>>
>> >> There is special code in the send_message_to_server_log
>> >function to make
>> >> sure it's written directly to the file.
>> >
>> >If the logger is complaining, it's quite possibly because it's
>> >unable to
>> >write to its file. Now that you mention it, doesn't this

>code go into
>> >infinite recursion if write_syslogger_file_binary() tries

>to ereport?
>> >

>>
>> I haven't looked at this part, it appears a separate (but closely
>> related) issue.
>>
>> Perhaps Andreas can comment on this?
>>
>> //Magnus

>
>Content-Description: stderr.patch
>
>[ Attachment, skipping... ]
>
>>
>> ---------------------------(end of

>broadcast)---------------------------
>> TIP 5: Have you checked our extensive FAQ?
>>
>> http://www.postgresql.org/docs/faq

>
>--
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 359-1001
> + If your life is a hard drive, | 13 Roberts Road
> + Christ can be your backup. | Newtown Square,
>Pennsylvania 19073
>


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 05:15 PM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com