My main server is down, so I am using my backup copy on a different
database.
Based on past posts I have read, this error is usually associated with
running out of memory for the query result. Problem is, I am only
expecting about 30 lines of moderate length to be returned I see
nothing in t
"Marcin Wasilewski" wrote:
>hello everybody,
>Can you help me?
>
>I have POSTGRESQL 7.0.3,
>I try to create simple view by typing.
>
>create view "xx" as select "aa.yy", "bb.yy" from "yy" order by "bb.yy"
>
>the problem is that parameter order is not implemented with create view.
You should rewrite your query using NOT EXISTS:
insert into LTable
select * from STable
where NOT EXISTS (
SELECT L.ID FROM LTable L
WHERE L.ID = ID);
This will use an index scan on LTable. This is also a FAQ item BTW.
Hope that helps,
Mike Mascari
[EMAIL PROTECTED]
-Original Message
Hi Tom,
[EMAIL PROTECTED]">"Brian J. France" <[EMAIL PROTECTED]> writes:
I am getting a few of these errors in my web logs and didn't know what I could do to stop it.
NOTICE: Deadlock detected -- See the lock(l) manual page for a possible cause.
Error in query "UPDATE SET = WHER
Hi !
Help me please to resolv my problem.
I have two tables . One of them is large (say 10 records)
with unique index on "ID"
and the second table (5000 records ) which i have to insert
into the first table , but the second table have much records,
which have many duplicate values in "ID" .
On Fri, 13 Apr 2001, Bruce Momjian wrote:
> Lamar Owen wrote:
> > As a matter of fact, I am an ordained Baptist minister. Don't
> > know about Bruce -- other than I like his catchy .sig... :-)
> Wow, pretty cool. I am just an underling. :-)
Well, we're all underlings. At most I can be an un
> On Fri, 13 Apr 2001, Karl DeBisschop wrote: > As for postgresql
> having an anit-Christian bias? I think Lamar and > Bruce, among
> others, could not be accused of an anti-Christian bias.
>
> Thanks, Karl.
>
> As a matter of fact, I am an ordained Baptist minister. Don't
> know about Bruce -
Justin Clift wrote:
> As an aside, did anyone ever step up to create a TPC-C benchmark suite for
> PostgreSQL?
Part of the Great Bridge QA process (on every beta, every community major and
minor release, and certainly any release we distribute on CD) is the running of
the TPC tests and the AS3AP
On Wed, Apr 11, 2001 at 06:32:50PM +, some SMTP stream spewed forth:
> Hi all:
>
> On page 29 of the PostgreSQL User's Guide, distributed with version 7.0.3,
> in table 3-8 Postgres Date Input, the last item in the Example column is
> January 8, 99 BC. The corresponding Description item rea
I'm trying to pull the current year with the following query:
select to_char(now(), '');
This is fine. Now, I would like to select this date in different time
zones.
Normally I just do:
select now() at time zone 'utc';
I guess I need a combination of the 2 queries above - one that asks fo
I'm putting together a small database to track communication with
our customers as we make some changes to our service. I want the
database to store a diary of all the email we have with each
customer on this subject, and I'm using BLOBs to store that
information.
I also want to have a timestamp
"Justin S." wrote:
>
> Thanks Tom. Yeah, I heard that an older version PostgreSQL was used. So if I
> just use a different port number, and not try replacing the version that
> comes with the OS, everything should work fine? How do I start PostgreSQL on
> a different port (and which would you rec
"Justin S." wrote:
>
> Thanks Tom. Yeah, I heard that an older version PostgreSQL was used. So if I
> just use a different port number, and not try replacing the version that
> comes with the OS, everything should work fine? How do I start PostgreSQL on
> a different port (and which would you rec
[EMAIL PROTECTED] writes:
> Should I worry?
Not unless you see that message frequently during routine operations.
Initial bulk data load doesn't count as routine ...
> How do I increase WAL_FILES?
See the documentation.
regards, tom lane
---(end
On Friday, April, 2001-04-13 at 18:34:06, Tom Lane wrote:
> > I've got a question: has anybody noticed in your production
> > tables, that updates on existing rows take longer than inserts
> > into those same tables?
>
> Updates naturally take longer than inserts. Especially if you haven't
> pro
Thanks Tom. Yeah, I heard that an older version PostgreSQL was used. So if I
just use a different port number, and not try replacing the version that
comes with the OS, everything should work fine? How do I start PostgreSQL on
a different port (and which would you recommend)? Thanks.
Sincerely,
"Justin S." <[EMAIL PROTECTED]> writes:
> Cobalt RaQ4i with version 6 of their operating system.
Oh. I think Cobalt has a Postgres (6.5.something?) installed as part of
the OS. You'll need to pick a different port number than 5432 to avoid
conflicting with the system's server.
BTW, I've heard
I dump database from 7.0.3 and attempting
to restore to 7.1rc4. And get the following
messages. I can reproduce them by
dropping new db and recreating new ones.
Line number varies from one restore to
the next and 'MoveOfflineLogs' message
was seen only once
Should I worry? How do I increase
W
"Justin S." <[EMAIL PROTECTED]> writes:
> IpcMemoryCreate: shmget failed (Permission denied) key=5432010, size=144,
> permission=700
Apparently you have an existing shm segment belonging to a different
userid. Did you previously start the postmaster under a different user?
If so you'll need to g
Cobalt RaQ4i with version 6 of their operating system.
Sincerely,
Justin Stayton
CometFly Media, LLC.
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Steve Wolfe
Sent: Friday, April 13, 2001 1:13 PM
To: [EMAIL PROTECTED]
Subject: Re: [
> First off, I'd just like to thank everyone for their help with my last
> problem. It worked, but now it gives me another error:
>
> IpcMemoryCreate: shmget failed (Permission denied) key=5432010, size=144,
> permission=700
> This type of error is usually caused by an improper
> shared memory or
John Havard <[EMAIL PROTECTED]> writes:
> Is there anyway to do this without having to resort to writing the
> functions in C or some other language?
You really cannot write datatype I/O functions in anything but C,
because the I/O functions have to deal in C-style strings, which are
not a SQL d
Steve Wampler <[EMAIL PROTECTED]> writes:
> I'm getting the following error from pg_dump when trying to
> dump a particular database:
> ==
> -> pg_dump logdb >logdb.dump
> pqWait() -- connection not open
> PQendcopy: resetting connection
"Brian J. France" <[EMAIL PROTECTED]> writes:
> I am getting a few of these errors in my web logs and didn't know what I could do
>to stop it.
> NOTICE: Deadlock detected -- See the lock(l) manual page for a possible cause.
> Error in query "UPDATE SET = WHERE = " :
>ERROR: WaitOnLock:
First off, I'd just like to thank everyone for their help with my last
problem. It worked, but now it gives me another error:
IpcMemoryCreate: shmget failed (Permission denied) key=5432010, size=144,
permission=700
This type of error is usually caused by an improper
shared memory or System V IPC
Al <[EMAIL PROTECTED]> writes:
> begin work;
> select val from ids where cntr='ct1' for update;
> update ids set val=val+(some integer value) where cntr='ct1';
> commit work;
Looks reasonable.
> However, when I run everything except the commit on one terminal and
> then run up to and including t
> I've got a question: has anybody noticed in your production
> tables, that updates on existing rows take longer than inserts
> into those same tables?
Updates naturally take longer than inserts. Especially if you haven't
provided an index that allows the row(s) to be updated to be found
easily
Steve Wampler <[EMAIL PROTECTED]> writes:
> I need help - I've had a system crash that has left a table with some
> invalid OIDs. How do I clean this up? If I try a vacuum analyze,
> I get:
> configdb=# vacuum analyze;
> NOTICE: Rel attributes_table: TID 3304/23: OID IS INVALID. TUPGONE 1.
> N
Hi Tony,
That's great to hear. :-)
You need a saying like "'twas a long hard battle, but in the end we
emerged victorious" about now. Heh Heh Heh
Tony Grant wrote:
> Does not work, must be "host db_name IP user ident"
>
> Maybe this has something to do with java security???
Dunno. Errr...
Stan Brown <[EMAIL PROTECTED]> wrote:
>I am having a bit of trouble geting PostgreSQL working quite corectly on my
>fresh Debian "stable" istall.
>
>I installed it using the Debina dselect tool. Now, If I su - postgres, I
>can use psql to connect to the db, so I know that that part of the install
On 12 Apr 2001 22:40:56 +1000, Justin Clift wrote:
> When we installed Tomcat and PostgreSQL, I just copied the
> postgresql.jar file into the /lib directory inside the tomcat
> installation directory...
Justin wins the case of champagne (virtual for the time being)
The secret is there - where
I am having a bit of trouble geting PostgreSQL working quite corectly on my fresh
Debian "stable" istall.
I installed it using the Debina dselect tool. Now, If I su - postgres, I can use
psql to connect to the db, so I know that that part of the install went OK. However
I am having a problem addi
Hi all,
I've just taken a bit of time to give a more organised look to the whole
techdocs.postgresql.org website.
If anyone has a few moments spare, could they please take a look and
tell me what they think? I like it, but if most people don't, I'll
change it back.
Regards and best wishes,
Ju
Hi,
I have some code which legitimately tries to call
setObject(n,o) where o is an Object, and is null. The jdbc driver doesn't check
for this type, and as a result fails.
This is how I changed the code to deal with
this.
public void setObject(int parameterIndex,
Object x) throws
Justin S. writes:
> /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
>
> I get the following error:
>
> FATAL: StreamServerPort: bind() failed: Address already in use
> Is another postmaster already running on that port?
> If not, remove socket node (/tmp/.s.PGSQL.5432) an
On Thu, Apr 12, 2001 at 11:20:29PM -0400, Justin S. wrote:
> Hi Everyone,
>
> Alright, I've installed PostgreSQL 7.0.3 succesfully, but I still have a
> problem. When I try starting the PostgreSQL server, using the following
> command:
>
> /usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data
Hi,
Did you stop the postmaster with an SIGKILL ???
Just go into temp directory and delete file .s.PGSQL.5432
After try to restart postmaster. PostgreSQL
check this file in order to know if an another postmaster is running, so if you kill
postmaster, it dosen't
delete this file.
Cheers,
PEJA
37 matches
Mail list logo
