Hi
I installed 8.1.4 POSTGRESQL RPMS on my system. When I tried to run
/etc/init.d/postgresql start I got this error.
[EMAIL PROTECTED] init.d]# ./postgresql start
Initializing database: mkdir: cannot create directory
`/var/lib/pgsql/data/pg_log': File exists
[FAILED]
Starting postgresql se
Recently I have been put on a project that uses DB2 (not my choice). I am
using functions for reports and was told this may not be allowed. They
said:
One gap is the ability to tune the code in the function (not really static)
or to perform real-time analysis of performance problems.
I normall
On Thu, 30 Nov 2006 18:12:31 +0200
"Milen A. Radev" <[EMAIL PROTECTED]> wrote:
> We have a big DB that's backuped nightly using pg_dump in the custom
> format. Most of its size are several thousand large objects. During
> the dump of those LO the machine is heavily loaded so we are looking
> for a
We have a big DB that's backuped nightly using pg_dump in the custom
format. Most of its size are several thousand large objects. During
the dump of those LO the machine is heavily loaded so we are looking
for a way to "optimise" that part of backup process. We had an idea to
backup the DB but wit
Hmm, not entirely true. You may well only see the error in the process
itself.
Geoffrey wrote:
Alvaro Herrera wrote:
John Allgood wrote:
Hey Tom
I assume that if it is the kernel running out of descriptors that I
would get the messages in dmesg. This message only appears in the log
file
Tom Lane wrote:
Geoffrey <[EMAIL PROTECTED]> writes:
Alvaro Herrera wrote:
Yes. Which is kinda weird, because Postgres actually tests the number
when it starts, so that if you set the number too high, it will decrease
it according to what the kernel allows.
Maybe the test is newer than the ve
Geoffrey <[EMAIL PROTECTED]> writes:
> Alvaro Herrera wrote:
>> Yes. Which is kinda weird, because Postgres actually tests the number
>> when it starts, so that if you set the number too high, it will decrease
>> it according to what the kernel allows.
>>
>> Maybe the test is newer than the versi
Tom Lane wrote:
Geoffrey <[EMAIL PROTECTED]> writes:
I work with the original poster and wanted to make sure the problem here
is clear. The 'out of file descriptors' message is coming from
Postgresql, not the kernel. Thus, it doesn't make sense to me that the
max_files_per_process setting is
Geoffrey <[EMAIL PROTECTED]> writes:
> I work with the original poster and wanted to make sure the problem here
> is clear. The 'out of file descriptors' message is coming from
> Postgresql, not the kernel. Thus, it doesn't make sense to me that the
> max_files_per_process setting is too high.
Alvaro Herrera wrote:
Geoffrey wrote:
Okay, I'm just not getting it. Postgres complains that it is out of
file descriptors. The kernel is not complaining about any such issues.
So I should lower the max_files_per_process
value and this will rid us of the 'out of f
Maybe the whole problem is with ulimit. Ulimit sets the max files per
user at the shell and postgres might be exceeding the 1024 limit. What
would increasing this value to 2048 do?
Geoffrey wrote:
> Alvaro Herrera wrote:
>> Geoffrey wrote:
>>> Alvaro Herrera wrote:
John Allgood wrote:
> H
Geoffrey wrote:
> Okay, I'm just not getting it. Postgres complains that it is out of
> file descriptors. The kernel is not complaining about any such issues.
>
>
> So I should lower the max_files_per_process
> value and this will rid us of the 'out of file descripto
Bradley Kieser wrote:
Hmm, not entirely true. You may well only see the error in the process
itself.
You're telling me that the kernel could be running out of file
descriptors and I wouldn't see a message regarding this in the kernel
logs? I don't believe that is possible.
Geoffrey wrot
Alvaro Herrera wrote:
Geoffrey wrote:
Alvaro Herrera wrote:
John Allgood wrote:
Hey Tom
I assume that if it is the kernel running out of descriptors that I
would get the messages in dmesg. This message only appears in the log
file for that database.
Yeah, the point is that you have the ma
Geoffrey wrote:
> Alvaro Herrera wrote:
> >John Allgood wrote:
> >>Hey Tom
> >>
> >>I assume that if it is the kernel running out of descriptors that I
> >>would get the messages in dmesg. This message only appears in the log
> >>file for that database.
> >
> >Yeah, the point is that you have t
Alvaro Herrera wrote:
John Allgood wrote:
Hey Tom
I assume that if it is the kernel running out of descriptors that I
would get the messages in dmesg. This message only appears in the log
file for that database.
Yeah, the point is that you have the max_files_per_process setting
higher tha
Shane Ambler wrote:
> I don't see that as being the case - there will be exceptions where
> you have new features in an 8.x database that won't work in a 7.x db
> but otherwise it shouldn't matter, the dumps can be used to import
> into other databases than postgres as long as you use dump with
> i
Alvaro Herrera wrote:
> John Allgood wrote:
>
>> Hey Tom
>>
>> I assume that if it is the kernel running out of descriptors that I
>> would get the messages in dmesg. This message only appears in the log
>> file for that database.
>>
>
> Yeah, the point is that you have the max_files_pe
Richard Broersma Jr wrote:
My understanding is that dumps are not backwards compatible. Any dumps created
with a Version 8.*
pg_dump cannot be used for any older versions. If you want "play it safe" you
should create a new
server for the postgresql version 8.1 to preform validation tests wit
19 matches
Mail list logo
