11 9:40 AM
To: Mcleod, John
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] pgsql error
On Tue, Jul 26, 2011 at 7:47 AM, Mcleod, John wrote:
> Thank you for the reply.
>
> At command line, I ran...
> "psql --version"
> and received..
> "psql (PostgreSQL) 7.5
"Mcleod, John" writes:
> Thank you for the reply.
> At command line, I ran...
> "psql --version"
> and received..
> "psql (PostgreSQL) 7.5devel"
Egad. That is an early development snapshot of what eventually got
called the 8.0 release. You should try "select version();" in psql
to verify that
On Tue, Jul 26, 2011 at 7:47 AM, Mcleod, John wrote:
> Thank you for the reply.
>
> At command line, I ran...
> "psql --version"
> and received..
> "psql (PostgreSQL) 7.5devel"
>
> The database is sitting on a Windows 2003 Server box.
> A mapping application, wrote in PHP, runs with Apache 2.05
John
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Monday, July 25, 2011 11:20 PM
To: Merlin Moncure
Cc: Mcleod, John; pgsql-general@postgresql.org
Subject: Re: [GENERAL] pgsql error
Merlin Moncure writes:
> On Mon, Jul 25, 2011 at 3:05 PM, Mcleod, John w
Merlin Moncure writes:
> On Mon, Jul 25, 2011 at 3:05 PM, Mcleod, John wrote:
>> I'm receiving the following error
>> CONTEXT: writing block 614 of relation 394198/412175
>> WARNING: could not write block 614 of 394198/412175
>> DETAIL: Multiple failures --- write error may be permanent.
>> ERROR
On Mon, Jul 25, 2011 at 3:05 PM, Mcleod, John wrote:
> Hello all,
>
> I'm new to pgsql and I'm taking over for a project manager that left the
> company.
>
> I'm receiving the following error…
>
>
>
> CONTEXT: writing block 614 of relation 394198/412175
>
> WARNING: could not write block 614 of 39
2011/7/25 Mcleod, John :
> Hello all,
>
> I'm new to pgsql and I'm taking over for a project manager that left the
> company.
>
> I'm receiving the following error…
>
>
>
> CONTEXT: writing block 614 of relation 394198/412175
>
> WARNING: could not write block 614 of 394198/412175
>
> DETAIL: Multi
Hello all,
I'm new to pgsql and I'm taking over for a project manager that left the
company.
I'm receiving the following error...
CONTEXT: writing block 614 of relation 394198/412175
WARNING: could not write block 614 of 394198/412175
DETAIL: Multiple failures --- write error may be permanent.
ER
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> I have a PostgreSQL 8.2.6 on FreeBSD 6.3 (but the described behavior
> appears during several earlier minor versions as well) - which powers a
> php based web application. What I experience is the message (below)
> which appears during the first
[EMAIL PROTECTED] wrote:
> Alvaro Herrera wrote:
>> It's not unlikely that the server is crashing. This should not happen.
>> Please examine the logs and let us know what you find.
>>
>> If it's indeed crashing, we would like to see a more complete report
>> (possibly including a backtrace from a
Alvaro Herrera wrote:
It's not unlikely that the server is crashing. This should not happen.
Please examine the logs and let us know what you find.
If it's indeed crashing, we would like to see a more complete report
(possibly including a backtrace from a core dump).
I enabled the highest lev
[EMAIL PROTECTED] wrote:
> I have a PostgreSQL 8.2.6 on FreeBSD 6.3 (but the described behavior
> appears during several earlier minor versions as well) - which powers a
> php based web application. What I experience is the message (below)
> which appears during the first 5-7 clicks after the
Jorge Godoy wrote:
Have you checked your code and seen what is really happening on these clicks?
I have been trying to catch the error from within php, however
PostgreSQL (in the described case) dies in a way which does not return
any error.
The error returned is that php can't connect to t
Em Monday 04 February 2008 08:42:16 [EMAIL PROTECTED] escreveu:
> I have a PostgreSQL 8.2.6 on FreeBSD 6.3 (but the described behavior
> appears during several earlier minor versions as well) - which powers a
> php based web application. What I experience is the message (below)
> which appears duri
I have a PostgreSQL 8.2.6 on FreeBSD 6.3 (but the described behavior
appears during several earlier minor versions as well) - which powers a
php based web application. What I experience is the message (below)
which appears during the first 5-7 clicks after the database has been
cleanly imported
My sysadmin just called and tol me he updated the php.rpm... he happens to
be in California totally
across the US from me for a week...
So I check the ver and...
Php version 4.1.2-7.2.6 recently updated - yesterday
Postgresql 7.3.3 installed in august sometime - upgraded from basic redhat
7.2 post
16 matches
Mail list logo
