Michael Fuhr <[EMAIL PROTECTED]> writes:
> I'm wondering if the error means you're missing that function, which
> is used to compare oid values.
A system without oideq would be so dead in the water it's not funny ---
consider that all the major catalogs are indexed by oid. It sounds to
me that on
Hello,
I was installing the Windows version of PostgreSQL 8.0.3 (I am running
Windows XP Home) when I got to the screen that asks for a password, I left
if blank and went to the next screen. I decided to go back and change it but
now I get "Account error. Invalid username specified" and can't
Thanks for the tip, but unfortunately id didn't address any of my
concerns. I alreay use the version 8, and I'm aware of the possibility
of using arrays for the results, which allows for some flexibility. But
unfortunately arrays are not records, and I'm limited to values of the
same types, and
Hi,
I am using PostgreSQL 7.4.2 on HP-UX systems. I am trying to pg_restore a
dump created using pg_dump with the following command-line:
pg_dump -Fc -fcerdump -Uemt -p10864 cer
The dump only has one table "emt_str", with integers and strings as its
attributes. Essentially, the table stores some
On Thu, Jul 14, 2005 at 03:38:19PM -0700, Chris White (cjwhite) wrote:
> Sorry, the exact error message is
>
> could not identify operator 184.
>
> I saw it in the syslog error log. At the moment I can't tell what was
> going on when it happened.
What version of PostgreSQL are you running? I'l
Sorry, the exact error message is
could not identify operator 184.
I saw it in the syslog error log. At the moment I can't tell what was
going on when it happened.
-Original Message-
From: Michael Fuhr [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 14, 2005 3:27 PM
To: Chris White (cjw
On Thu, Jul 14, 2005 at 01:48:38PM -0700, Chris White (cjwhite) wrote:
> Anybody have any idea why the error message "cannot identify operator
> 184" should be output. Also, what does it mean as to the state of the
> database, do we need to do anything to correct a problem?
Is that the *exact* err
-Original Message-
From: Michael Fuhr [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 14, 2005 3:27 PM
To: Chris White (cjwhite)
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Error message: cannot identify operator 184
On Thu, Jul 14, 2005 at 01:48:38PM -0700, Chris White (cjwhite
Anybody have any
idea why the error message "cannot identify operator 184" should be output.
Also, what does it mean as to the state of the database, do we need to do
anything to correct a problem?
Chris
On Monday 11 July 2005 22:05, [EMAIL PROTECTED] wrote:
| Ok, I am new to this backend arena for Postgres. I have been reading to
| find out how to take a oracle database and put it into a postgres
| database. Can someone refer me to a note, article, etc, that explains
| the process in detail.
th
On Tue, 12 Jul 2005, [iso-8859-1] Sebastian Kühner wrote:
> Hello,
>
> I'm new here in this group... and I hope that I find the solution for my
> problem here.
>
> I wrote a simple function which looks like this:
>
> CREATE OR REPLACE FUNCTION watchdog() RETURNS TIME AS '
> DECLARE
> watchdog_c
Ezequiel Tolnay <[EMAIL PROTECTED]> writes:
> I just can't get used to the annoyance of having to create a type for
> every single function that returns a rowset. It is frankly cumbersome.
Yup. See coming attractions at, eg,
http://developer.postgresql.org/docs/postgres/xfunc-sql.html#XFUNC-OUTP
Rainer J. H. Brandt wrote:
A while ago we had a client running PostgreSQL on a Quad v440, and the
performance was horrific. There are some known issues with PostgreSQL
and solaris. AFAIK there was a kernel patch to alleviate some of the
issues, but i'm unsure of the state of this as its been so
13 matches
Mail list logo
