On 12/1/06, Manish Pillai <[EMAIL PROTECTED]> wrote:
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_
On 12/1/06, Aaron Bono <[EMAIL PROTECTED]> wrote:
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 re
Steve Holdoway написа:
> 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
Hi all. I have a big .sql file written in postgres and i would like to know if
someone knows a tool to produce documentation from the .sql file
Kind Regards,
Antonios
-
Everyone is raving about the all-new Yahoo! Mail beta.
> > Replicate it???
>
> I'm hesitant about replacing backup with replication. It seems to me
> like trying to shoot a mosquito with a cannon.
One some threads that I've read, some posters mention that once their databases
reach a certain
size threshold, backups times become so large that replic
On Fri, 2006-12-01 at 10:06 -0800, Richard Broersma Jr wrote:
> > > Replicate it???
> >
> > I'm hesitant about replacing backup with replication. It seems to me
> > like trying to shoot a mosquito with a cannon.
>
> One some threads that I've read, some posters mention that once their
> databas
Hello Admin List!
I've had some adventures this morning with our db following an overheat
of the machine the night before (gratis of our hosting facility's
cooling problem). The system came back up following a box restart, and
postgres seemed to recover well. However, attempting to create a ta
Kim <[EMAIL PROTECTED]> writes:
> In looking around the catalogs to try and see any more clues, I took a
> look at pg_namespace. There were temp table namespaces listed there,
> however there should be no temp tables on the system right now at all.
This is normal.
> Is there a clean way to cle
Tom,
I can't thank you enough. It was pg_attribute, and a reindex cleared up
the problem.
regards, kim
Tom Lane wrote:
Kim <[EMAIL PROTECTED]> writes:
In looking around the catalogs to try and see any more clues, I took a
look at pg_namespace. There were temp table namespaces listed ther
Peter Wilson <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Could you show us the unmodified output from pg_restore -l, as well as
>> the edits you made to produce the -L script?
> Raw output from pg_restore -l is as follows:
Hm, this shows only data entries. Was the original pg_dump made with
On Fri, 2006-12-01 at 15:15 +0530, Rajesh Kumar Mallah wrote:
> I think the gap is genuine.
I think you need to take a look at the EnterpriseDB Debugger.
It solves the problem, so I suggest you take a look.
Open Source versions are available, AFAIK.
--
Simon Riggs
EnterpriseD
On 12/1/06, Rajesh Kumar Mallah <[EMAIL PROTECTED]> wrote:
On 12/1/06, Aaron Bono <[EMAIL PROTECTED]> wrote:
>
> 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 abili
Tom Lane wrote:
> Peter Wilson <[EMAIL PROTECTED]> writes:
>
>> Tom Lane wrote:
>>
>>> Could you show us the unmodified output from pg_restore -l, as well as
>>> the edits you made to produce the -L script?
>>>
>
>
>> Raw output from pg_restore -l is as follows:
>>
>
> Hm, th
Peter Wilson <[EMAIL PROTECTED]> writes:
> Partly the question might be 'what does the error message mean?' - it
> almost looks like do_restore doesn't think it has a real file underneath
> it, instead something that only provides sequential access.
That is certainly what the code thinks; as to wh
Aaron Bono wrote:
> I was told that, for DB2, stored procedures are a better choice for
> parameterized views which is what I was trying to do with the
> functions. Is the same true for PostgreSQL?
That depends somewhat on the meaning of "better", but on average a view
should be preferred if pos
Tom Lane wrote:
> Peter Wilson <[EMAIL PROTECTED]> writes:
>> Tom Lane wrote:
>>> Could you show us the unmodified output from pg_restore -l, as well as
>>> the edits you made to produce the -L script?
>
>> Raw output from pg_restore -l is as follows:
>
> Hm, this shows only data entries. Was th
I am battling a performance issue and was wondering if someone could
help. PostgreSQL 8.1.5, FreeBSD.
I have a very intense stored procedure which performs real time
aggregation of data.
I captured the stored procedure calls from a production system and
pumped them through psql, logging duration
17 matches
Mail list logo
