I changed from postgresql to mysql and everything now is great ;)
Same machine, same os, etc...
On 6/2/05, Roman Neuhauser <[EMAIL PROTECTED]> wrote:
> # [EMAIL PROTECTED] / 2005-05-03 17:56:53 -0300:
> > The FreeBSD is the last STABLE version. I can try to change some
> > hardware, I already
# [EMAIL PROTECTED] / 2005-05-03 17:56:53 -0300:
> The FreeBSD is the last STABLE version. I can try to change some
> hardware, I already changed memory, what can I try now ? the processor
> ? motherboard ??
> On 5/3/05, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> > On Tue, 2005-05-03 at 15:04,
On Tue, 2005-05-03 at 15:56, Alexandre Biancalana wrote:
> Ohhh god :(
>
> The FreeBSD is the last STABLE version. I can try to change some
> hardware, I already changed memory, what can I try now ? the processor
> ? motherboard ??
You're running FreeBSD 5, right? I'd try to find the last ve
Ohhh god :(
The FreeBSD is the last STABLE version. I can try to change some
hardware, I already changed memory, what can I try now ? the processor
? motherboard ??
On 5/3/05, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-05-03 at 15:04, Alexandre Biancalana wrote:
> > Thank you f
On Tue, 2005-05-03 at 15:04, Alexandre Biancalana wrote:
> Thank you for the detailed explanation Scott, they are very handy !!
>
> I reduced the shared_buffers to 32768, but the problem still occurs.
>
> Any other idea ??
Yeah, I had a sneaking suspicion that shared_buffers wasn't causing t
Thank you for the detailed explanation Scott, they are very handy !!
I reduced the shared_buffers to 32768, but the problem still occurs.
Any other idea ??
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister co
On Tue, 2005-05-03 at 12:25, Alexandre Biancalana wrote:
> On 5/3/05, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> > On Tue, 2005-05-03 at 11:36, Alexandre Biancalana wrote:
> > > >>You need to find out what's triggering that. Turning on query logging
> > > >>would be a good way of investigating.
>
On 5/3/05, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-05-03 at 11:36, Alexandre Biancalana wrote:
> > >>You need to find out what's triggering that. Turning on query logging
> > >>would be a good way of investigating.
> >
> > Which directives can I use to enable this ?
> > debug_prin
On Tue, 2005-05-03 at 11:36, Alexandre Biancalana wrote:
> >>You need to find out what's triggering that. Turning on query logging
> >>would be a good way of investigating.
>
> Which directives can I use to enable this ?
> debug_print_parse ? debug_print_rewritten ? debug_print_plan ?
> debug_pr
On Tue, May 03, 2005 at 10:37:03AM -0600, Michael Fuhr wrote:
>
> Signal 10 is SIGBUS (bus error) on FreeBSD 4.11. Somewhere under
> $PGDATA there might be a core dump named postmaster.core
Correction: the core dump should be named postgres.core (at least
it is on my FreeBSD 4.11-STABLE system i
On Tue, May 03, 2005 at 01:36:13PM -0300, Alexandre Biancalana wrote:
>
> The system does not generate core dump file for this error.
Are you sure? Where did you look and what file name did you look
for? Unless you've changed the kern.corefile sysctl setting, the
file should be named "post
>>You need to find out what's triggering that. Turning on query logging
>>would be a good way of investigating.
Which directives can I use to enable this ?
debug_print_parse ? debug_print_rewritten ? debug_print_plan ?
debug_pretty_print ?
>>Rather large, shared buffers for a machine with only
On Tue, May 03, 2005 at 09:54:03AM -0500, Scott Marlowe wrote:
>
> You might want to look in your signal man page on BSD and see what
> signal 10 means. On solaris it's a bus error. Not a clue what it is in
> FreeBSD myself though.
Signal 10 is SIGBUS (bus error) on FreeBSD 4.11. Somewhere und
oops... you were writing about signal 10 not signal 11. my bad - sorry
On 5/3/05, Vlad <[EMAIL PROTECTED]> wrote:
> Alexandre,
>
> I saw reports (and observed the problem myself) that all sort of
> different softwares suffering from signal 11 under FreeBSD (more often
> seen on 5-STABLE). So far
Alexandre,
I saw reports (and observed the problem myself) that all sort of
different softwares suffering from signal 11 under FreeBSD (more often
seen on 5-STABLE). So far the collection is: Apache 1.3 (myself),
Mysql (recent descussion on freebsd-stable list) and now postgresql...
The hardware i
On Tue, 2005-05-03 at 08:39, Alexandre Biancalana wrote:
> Hi list,
>
> I'm running postgresql 8.0.1 on FreeBSD 4.11-STABLE, the machine is
> and AMD Sempron 2.2, 1GB Ram..
>
> I use postgresql as database for dspam, an spam classification
> program. This database have and moderated use, on ave
Alexandre Biancalana <[EMAIL PROTECTED]> writes:
> Watching postgresql logs I see the following messages ocurs a lot of
> times in a day:
> May 3 06:58:44 e-filter postgres[250]: [21-1] LOG: server process
> (PID 59608) was terminated by signal 10
You need to find out what's triggering that. T
Hi list,
I'm running postgresql 8.0.1 on FreeBSD 4.11-STABLE, the machine is
and AMD Sempron 2.2, 1GB Ram..
I use postgresql as database for dspam, an spam classification
program. This database have and moderated use, on averange 10
simultaneous conections executing relative big queries using "
18 matches
Mail list logo
