Patrick Krecker writes:
> As expected, the following fails:
> select count from foo;
> ERROR: column "count" does not exist
> LINE 1: select count from foo;
>^
> But if I change the syntax to something I thought was equivalent:
> select foo."count" from foo;
> count
> ---
>
Sorry, I changed the email as I was writing it but I forgot to change the
subject line. An appropriate subject would be 'Strange behavior when
referencing non-existent column foo."count".'
On Wed, Dec 17, 2014 at 2:50 PM, Patrick Krecker
wrote:
>
> I encountered this today and it was quite surpri
I encountered this today and it was quite surprising:
select version();
version
--
PostgreSQL 9.3.5 on x86_64-unknown-linux-gnu, compiled by gcc (Ubu
On 06/20/2014 01:18 AM, Dick Kniep wrote:
Hi list,
...
Now recently I have noticed a strange problem.
...
psycopg2.DatabaseError: SSL error: ccs received early
Did you try Googling "SSL error: ccs received early"? Like Adrian, I
suspect your answer will be found in one of those messages. What
On 06/20/2014 01:18 AM, Dick Kniep wrote:
Hi list,
We have been using Postgresql for more than a decade now. Never had any real
problems. Thank you very much for this great product.
Now recently I have noticed a strange problem.
Below is a traceback of a python program using psycopg and this
Hi list,
We have been using Postgresql for more than a decade now. Never had any real
problems. Thank you very much for this great product.
Now recently I have noticed a strange problem.
Below is a traceback of a python program using psycopg and this correlates with
the postgresql log below th
hubert depesz lubaczewski writes:
> On Fri, Sep 04, 2009 at 05:42:31PM +0800, Juan Backson wrote:
>> When I tried to add the following index, I get some strange error. Does
>> anyone know what these errors mean and how to fix it?
>> Here is the index query:
>> create index idx_product_items_digi
On Fri, Sep 04, 2009 at 05:42:31PM +0800, Juan Backson wrote:
> When I tried to add the following index, I get some strange error. Does
> anyone know what these errors mean and how to fix it?
> Here is the index query:
> create index idx_product_items_digits on product_items using gist (digits
> g
Hi,
When I tried to add the following index, I get some strange error. Does
anyone know what these errors mean and how to fix it?
Here is the index query:
create index idx_product_items_digits on product_items using gist (digits
gist_prefix_range_ops,product_id)
Here is the error:
NOTICE: __p
Hi,
Working on postgres8.1 in PHP, I came in the situation I needed to
create a derived table.
Consider the following query:
SELECT tempwordstable.zoekwoord, CV.categoryvalueid, CV.categoryid,
CV.shortdesc
FROM tblcategoryvalues AS CV,
( (SELECT 'mark' AS zoekwoord) UNION (SELECT 'test' AS
> create table fp1(a text, b text, primary key(a,b));
> create table foo (a text, b numeric, c text);
>
> insert into foo select 'a', 1, explode_array(string_to_array('a,b',
> ',')); -- works
> truncate foo;
> alter table foo add foreign key(a,b) references fp1(a,b) on delete cascade;
>
> insert
I got the error mesage,
ERROR: could not find relation 19693 among query result relations,
from a strange interaction between inser, foreign keys and a udf.
After a but of trial and error, I came up with a test case:
create or replace function explode_array(in_array anyarray) returns
setof any
> There's probably not much more we can learn at this point --- given
> that the entry is old, any other evidence is probably long gone.
I'm afraid I'll never be able to get soon enough to the evidence even if
it happens again, unless I manage to reproduce it myself, which I tried
but didn't succe
Csaba Nagy <[EMAIL PROTECTED]> writes:
>> Is this xmin quite a bit older than what you get for a freshly-created
>> temp table?
> I would say yes, this is a test system which is highly stressed from
> time to time, but does not get continuous load.
OK, so it seems we have an old pg_type entry t
> Is this xmin quite a bit older than what you get for a freshly-created
> temp table?
I would say yes, this is a test system which is highly stressed from
time to time, but does not get continuous load.
test03=> select oid, xmin from pg_type where typname = 'temp_report';
oid| xmin
--
Csaba Nagy <[EMAIL PROTECTED]> writes:
> I executed what you suggest below, see the results below. Short
> conclusion: the type is there in pg_type, the relation is not there in
> pg_class. Is there anything I should look for more ?
> test03=> select oid, xmin from pg_type where typname = 'temp_re
On Fri, 2006-09-01 at 11:25, Csaba Nagy wrote:
> I executed what you suggest below [snip]
Ok... it looks like the postgres version is not what I expected and
reported in the first mail, but:
test03=> select version();
version
I executed what you suggest below, see the results below. Short
conclusion: the type is there in pg_type, the relation is not there in
pg_class. Is there anything I should look for more ?
Cheers,
Csaba.
> BTW, when this happens, does the error persist? If it's a race
> condition you'd expect not
Csaba Nagy <[EMAIL PROTECTED]> writes:
> create temp table temp_report ...;
> ... do some processing using this table...
> drop table temp_report;
> commit;
> This code occasionally triggered the following error (couldn't reliably
> reproduce):
> ERROR: type "temp_report" already exists
B
Csaba Nagy <[EMAIL PROTECTED]> writes:
> In any case, the error message is strange in itself, as if I try to
> create the temporary table when it exists, the error I get in manual
> trial is:
> ERROR: relation "test_temp_table" already exists
>
> compared to the error from the OP
Csaba Nagy wrote:
In any case, the error message is strange in itself, as if I try to
create the temporary table when it exists, the error I get in manual
trial is:
ERROR: relation "test_temp_table" already exists
compared to the error from the OP which I cite here for referen
On Thu, 2006-08-31 at 17:25, Alban Hertroys wrote:
> Csaba Nagy wrote:
> > The code is possible to be executed in parallel by multiple threads, on
> > different connections, or in sequence on the same connection. I would
> > expect it in both cases to work correctly... in manual tests I was able
>
Csaba Nagy wrote:
The code is possible to be executed in parallel by multiple threads, on
different connections, or in sequence on the same connection. I would
expect it in both cases to work correctly... in manual tests I was able
to create in parallel temporary tables named identically in diffe
Postgres version: 8.1.3
I have a code similar to this pseudo-code:
try {
create temp table temp_report ...;
... do some processing using this table...
drop table temp_report;
commit;
} catch all errors {
rollback;
}
This code occasionally triggered the following error (couldn't reliabl
"Christian Rengstl" <[EMAIL PROTECTED]> writes:
> Unfortunately it's windows, but nevertheless it worked now for weeks
> and suddenly the postgre user should not be able to copy anymore?
Broken anti-virus software. We've seen essentially identical reports
before ...
regar
Disk full or otherwise problems with the disk?
I remember I saw somthing similiar some months ago and the reason was (AFAIR)
something like a full partition or a partition set to readonly, or a broken
mountpoint because of hardware errors. With Linux, not MSW.
Regards, Frank
On Wed, 02 Aug 20
The thing is that the very same file was copied to the specified directory.
Martijn van Oosterhout wrote on 08/02/06 9:43 am:
> On Wed, Aug 02, 2006 at 09:34:25AM +0200, Christian Rengstl wrote:
>> it seems as if in /pg_xlog/archive_status the respective file
>> 0001002000D2.ready was
Unfortunately it's windows, but nevertheless it worked now for weeks and
suddenly the postgre user should not be able to copy anymore? Besides, the file
was copied and then disappeared from the pg_xlog directory, nevertheless
postgre kept trying to copy the very same file.
"A. Kretschmer" <[EMA
On Wed, Aug 02, 2006 at 09:34:25AM +0200, Christian Rengstl wrote:
> it seems as if in /pg_xlog/archive_status the respective file
> 0001002000D2.ready was not changed to
> 0001002000D2.done. Can this be done manually? About the
> persmission denied error i still have absolu
am 02.08.2006, um 9:27:22 +0200 mailte Christian Rengstl folgendes:
> Postgre copied the file 0001002000D2 to the specified directory
> and now it says it can't be copied...I really, really don't get it!
My guess: Access Denied on the filesystem for the postgres-User.
PS.: Windows,
it seems as if in /pg_xlog/archive_status the respective file
0001002000D2.ready was not changed to
0001002000D2.done. Can this be done manually? About the persmission
denied error i still have absolutely no clue!
"Christian Rengstl" <[EMAIL PROTECTED]> wrote on 08/02/06
Hi everyone,
can please somebody let me know what this error message is supposed to mean:
ERROR: could not open relation 1663/16858/9469857: Permission denied
Strange thing about it is that i do not have a relation with that name.
This somehow seems to go along with this other strange error mess
Csaba Nagy <[EMAIL PROTECTED]> writes:
> ERROR: could not access status of transaction 0
> DETAIL: could not create file "/postgresdata/pg_subtrans/04E7": Die
> Datei existiert bereits
> The german text means "the file exists already".
I think we've finally identified the reason for this:
http:
Andrew Sullivan <[EMAIL PROTECTED]> writes:
> On Mon, Jan 16, 2006 at 09:27:30AM +0530, Mavinakuli, Prasanna (STSD) wrote:
>> ERROR: xlog flush request 0/108EA5F8 is not satisfied --- flushed only
>> to 0/1813C60
> If I had to guess, I'd say you're having a hard disk failure of some
> kind. In p
On Mon, Jan 16, 2006 at 09:27:30AM +0530, Mavinakuli, Prasanna (STSD) wrote:
>
> Hi,
>
> I am getting following strange errors while executing queries.
>
> 1)
> ERROR: xlog flush request 0/108EA5F8 is not satisfied --- flushed only
> to 0/1813C60
If I had to guess, I'd say you're having a hard
Hi,
I am getting following strange errors while executing queries.
1)
ERROR: xlog flush request 0/108EA5F8 is not satisfied --- flushed only
to 0/1813C60
CONTEXT: writing block 2 of relation 17142/16653
WARNING: could not write block 2 of 17142/16653
DETAIL: Multiple failures --- write error
Exact message of my second problem is:
WARNING: relation "rawlog" page 0 is uninitialized --- fixing
-Original Message-
From: Mavinakuli, Prasanna (STSD)
Sent: Monday, January 16, 2006 9:28 AM
To: pgsql-general@postgresql.org
Subject: Strange error while executing query from front end
When I try to do vacuum then also I am getting same error,warning
rather.
LOGARCHDB=# vacuum;
WARNING: relation "rawlog" page 2 is uninitialized --- fixing
WARNING: relation "rawlog" page 3 is uninitialized --- fixing
WARNING: relation "rawlog" page 2 is uninitialized --- fixing
WARNING: rel
OK, I should have included the postgres log this in the first place
beside only the JDBC log:
ERROR: could not access status of transaction 0
DETAIL: could not create file "/postgresdata/pg_subtrans/04E7": Die
Datei existiert bereits
The german text means "the file exists already".
Any advice
Hi all,
I wonder what caused the error we just got on a postgres 8.0.3 data base
(using JDBC to connect, but I guess that's not really relevant for this
error):
[snip stack trace]
Caused by: org.postgresql.util.PSQLException: ERROR: could not access
status of transaction 0
[snip]
Could it be som
Thank you for your reply, the procedure code (which I posted in the original
post) already utilizes the Execute statment.
Here is the weirdest thing. The error only occurs in the query window
that I originally wrote the code in. If I open another query window
(I'm using PGAdmin III), I can run th
On Tue, 2005-10-11 at 07:55 +0200, Sim Zacks wrote:
> I tried it on a test RedHat server
> PostgreSQL 8.0.2beta1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2
> 20020903 (Red Hat Linux 8.0 3.2-7)
> and the problem didn't occur. It is a slightly newer version, though,
> so it doesn't prove an
I tried it on a test RedHat server
PostgreSQL 8.0.2beta1 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2
20020903 (Red Hat Linux 8.0 3.2-7)
and the problem didn't occur. It is a slightly newer version, though,
so it doesn't prove anything. But the Gentoo is my production machine,
so I guess I'
Sim Zacks <[EMAIL PROTECTED]> writes:
> The version (from select version()) is
> PostgreSQL 8.0.1 on i686-pc-linux-gnu, compiled by GCC i686-pc-linux-gnu-gcc
> (GCC) 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)
Gentoo eh? When you run a bleeding-edge distribution, sometimes you get
n
qry_Customers_Country is a view.
There is no row in pg_class with relfilenode=7973197 either when it
works or after I get the error.
The version (from select version()) is
PostgreSQL 8.0.1 on i686-pc-linux-gnu, compiled by GCC i686-pc-linux-gnu-gcc
(GCC) 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3,
"Sim Zacks" <[EMAIL PROTECTED]> writes:
> I am receiving the following error and cannot understand what it means.
> Please let me know if this makes sense to you.
> ERROR: could not open relation 1663/3364852/7973197: No such file or
> directory
> CONTEXT: SQL statement "create temporary table t
I am receiving the following error and cannot understand what it means.
Please let me know if this makes sense to you.
ERROR: could not open relation 1663/3364852/7973197: No such file or
directory
CONTEXT: SQL statement "create temporary table tmpcust as select a.* from
qry_Customers_Country a"
Am Mittwoch, 13. Juli 2005 16:04 schrieb Tom Lane:
> Janning Vygen <[EMAIL PROTECTED]> writes:
> > I was just testing some configuration settings, especially increasing
> > shared_buffers and setting fsync to false. And suddenly it happens 3
> > times out of ten that i get this error.
>
> Could you
Janning Vygen <[EMAIL PROTECTED]> writes:
>PERFORM n.nspname ,c.relname
> FROM
> pg_catalog.pg_class c
> LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
> WHERE
> n.nspname like 'pg_temp_%'
> AND pg_catalog.pg_table_is_visible(c.oid)
> AND Upp
Janning Vygen <[EMAIL PROTECTED]> writes:
> I was just testing some configuration settings, especially increasing
> shared_buffers and setting fsync to false. And suddenly it happens 3 times
> out of ten that i get this error.
Could you put together a complete example --- that is a script someon
Hi,
[i am using Postgresql version 8.0.3]
yesterday i posted a mail regarding a function which calculates a ranking with
a plperl SHARED variable.
Today i ve got some problems with it:
FEHLER: duplizierter Schlüssel verletzt Unique-Constraint
»pg_type_typname_nsp_index«
CONTEXT: SQL-Anweis
Hans-Jürgen Schönig schrieb:
> ...
> I am writing a perl program that should insert data into a database. It
> works perfectly well when starting the script manually. When the
> starting the script as cron (same user), it collapses ($fehler = 32 512
> which I don't know and can't find).
>
> $fehl
Hi all,
I'm new to postgres. I started a project with msql, but the project
got bigger and bigger and I've reached the limits of msql, so I thought,
why not change to postgres.
Installing postgres went without any trouble (6.4.2 on a Solaris 2.5
machine). I exported all my tables made with msql a
53 matches
Mail list logo
