John Hughes <[EMAIL PROTECTED]> writes:
> The problem is that inserting into temp_holding takes more than a SECOND PER
> ROW!
Offhand I'd bet on the repeated computations of max(core_leads.id) as
being the bulk of the problem. That's completely broken anyway since
if concurrent insertions are ha
At 1:34 AM -0500 3/27/05, Madison Kelly wrote:
Dan Sugalski wrote:
At 12:31 AM -0500 3/27/05, Madison Kelly wrote:
Hi all,
After looking at the postres and perl docs plus some Googling I
can't seem to find the answer I am looking for. I hope maybe
someone here can help. ^_^
What I am trying
Vernon wrote:
> Just installed the 8.0 version for Windows. As a Unix
> guy, I would like to do things through the command
> prompt. I have trouble to bring up it. After bringing
> up the "psql to template1" as the same user of the
> installation configuration, it disappears right after
> I type in
I'm getting the following in the server log:
2005-03-27 06:04:21 GMT estat DETAIL: Process 20928 waits for ShareLock
on transaction 7751823; blocked by process 20929.
Process 20929 waits for ShareLock on transaction 7768115;
blocked by process 20928.
2005-03-27 06:04:21 GMT estat CONTEXT:
"David Parker" <[EMAIL PROTECTED]> writes:
> Is there a technical reason that the "or replace" syntax isn't supported
> for CREATE TRIGGER?
Lack of round tuits.
Does it seem like a high priority to you? I'd think that changes in the
trigger function (which you *can* do with CREATE OR REPLACE) wo
On Fri, 25 Mar 2005, Patrick TJ McPhee wrote:
In article <[EMAIL PROTECTED]>,
Paul Cunningham <[EMAIL PROTECTED]> wrote:
% I use a bash script (similar to following example) to update tables.
%
% psql -v passed_in_var=\'some_value\' -f script_name
%
% Is it possible to pass a value back from
Dan Sugalski wrote:
At 12:31 AM -0500 3/27/05, Madison Kelly wrote:
Hi all,
After looking at the postres and perl docs plus some Googling I
can't seem to find the answer I am looking for. I hope maybe someone
here can help. ^_^
What I am trying to do is turn off autocommit for one particular
Madison Kelly wrote:
>
>What I am trying to do is turn off autocommit for one particular task
> in my program. I realize I can turn off AutoCommit when I connect to the
> database but in this case that is not what I want to do. This is a
> one-off task.
>
>What I thought would work was:
>
PostgreSQL 8.0.0beta5 Documentation
Chapter 35.9 bottom of the page.
"RAISE EXCEPTION presently always generates the same SQLSTATE code,
P0001, no matter what message it is invoked with. It is possible
to trap this exception with EXCEPTION ... WHEN RAISE_EXCEPTION THEN ...
but there
At 12:31 AM -0500 3/27/05, Madison Kelly wrote:
Hi all,
After looking at the postres and perl docs plus some Googling I
can't seem to find the answer I am looking for. I hope maybe someone
here can help. ^_^
What I am trying to do is turn off autocommit for one particular
task in my program
Hi list
I have been posting about this problem with Dave Page and Magnus
Hagander on pgadmin-support because i first thought I had a problem with
pgAdmin. After further investigation Dave suggested that I post to this
list as I seem to have a more general problem.
In short the problem is that eve
Hi everybody ,
I tried using Postgre, but I have some
problems.
I create a constraint ( R1>=0 ), and after
connect to server from VFP via ODBC .
In the client program I turn on the transactions .
( SQLSETPROP(nHandle,'Transactions',2) )
When I run UPDATE statements one after the ot
> "AI" == Alexander Ivanko <[EMAIL PROTECTED]> writes:
AI> Hi!
AI> Could you please answer me whether PostgreSQL v7.4.7 (on x86 platform) is
AI> compatible with FreeBSD v5.3 or its safer to use FreeBSD v4.11?
AI> Excuse me for my English. Thank you in advance!
I use Postgres 7.4.7 on both Fre
> "SM" == Scott Marlowe <[EMAIL PROTECTED]> writes:
SM> Are you getting any output from the postgresql logs that would point to
SM> backends dieing or anything like that? This sounds like a networking /
SM> client problem to me.
Ok... well, I rebuilt the entire OS and postgres *without* the
> "SE" == Sarah Ewen <[EMAIL PROTECTED]> writes:
SE> Hi there folks,
SE> I've just had pg_dump fail on me for the first time ever, and I'm not
SE> sure why.
SE> It generates 24MB of dump before bombing out with:
SE> pg_dump: socket not open
SE> pg_dump: SQL command to dump the contents of ta
Just installed the 8.0 version for Windows. As a Unix
guy, I would like to do things through the command
prompt. I have trouble to bring up it. After bringing
up the "psql to template1" as the same user of the
installation configuration, it disappears right after
I type in the password, which is th
>> I'm trying to move existing ERP database to Postgres
>>
>> My database contains table of document headers:
>>
>> CREATE TABLE document (
>> category CHAR,
>> sequence NUMERIC(7),
>> ... a lot of other columns ... ,
>> PRIMARY KEY (category, sequence) ) ;
>>
>> and document rows:
>>
>> CREATE TAB
A copy of your registration form is provided below for your records:
===
The following data was entered into our database on March 24, 2005 at 09:06 AM
Product = PostgreSQL
Company = PostgreSQL Org
Listing Description =
Title = PostgreSQL
Hi, I've been working the past couple of days to import a bunch of csv data
into my system.
I have a temp_holding table which basically just matches the csv format.
I have a trigger before insert on each row on the temp_holding table, below.
The problem is that inserting into temp_holding takes
Hello,
I'm wondering if you can help. We are currently enabling QLR Manager
(http://www.qlrmanager.com) to work with PostgreSQL. QLR (Query, Layout
& Report) Manager is a php server based reporting and graphing tool that
currently works with Oracle and MySQL. It runs on most any javascript
ena
In article <[EMAIL PROTECTED]>,
Paul Cunningham <[EMAIL PROTECTED]> wrote:
% I use a bash script (similar to following example) to update tables.
%
% psql -v passed_in_var=\'some_value\' -f script_name
%
% Is it possible to pass a value back from psql to the bash script?
If you run it like
I have item table and many child tables where the items are used.
I want to merge two item codes into single item in all tables.
It is not nice to write a lot of separate UPDATE statements for each table.
So I want to utilize REFERENCES clause for merging.
I tried the following code but got dupli
Thomas,
thank you for reply. There was a typo in my code. Second table should be
CREATE TABLE info (
code1 CHAR(10),
code2 CHAR(10),
FOREIGN KEY ('1', code1) REFERENCES classifier,
FOREIGN KEY ('2', code2) REFERENCES classifier
);
I try to explain my problem more precicely.
I can implemen
Reply from Bruno Wolff III, re-posted from mail:
> >>I have 120 concurrent users inserting documents. Mostly they are using
> >>10
> >>different document types. Each type should have separate numbering.
> >>They
> >>insert 30 documents per minute in peak hours.
> >
> >You really should think abou
Is there a
technical reason that the "or replace" syntax isn't supported for CREATE
TRIGGER?
-
DAP--David
Parker Tazz Networks (401)
709-5130
Hi all,
After looking at the postres and perl docs plus some Googling I can't
seem to find the answer I am looking for. I hope maybe someone here can
help. ^_^
What I am trying to do is turn off autocommit for one particular task
in my program. I realize I can turn off AutoCommit when I con
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> It seems HISTORY has not been updated yet. Is this intended?
Someone (probably Bruce or me) will do release notes before the
release. This is just a beta to find out if we broke anything ...
regards, tom lane
---
> In order to provide more extensive testing for 8.0.2, we have just
> packaged up a Beta1 available from:
>
> http://www.postgresql.org/ftp/source/v8.0.2beta1/
>
> The major reason for this release is the ARC->2Q changes that Tom has
> implemented.
>
> Our plan is to do a full release n
In order to provide more extensive testing for 8.0.2, we have just
packaged up a Beta1 available from:
http://www.postgresql.org/ftp/source/v8.0.2beta1/
The major reason for this release is the ARC->2Q changes that Tom has
implemented.
Our plan is to do a full release next Thursday ...
Hi folks, I am building PostgreSQL 8.01 on a Linux Mandrake 10.1 machine.
The commands:
configure
gmake
gmake install
operates without errors
The problem is with:
gmake check
67 of 96 tests fail !!
The erros are caused by the postmaster not responding error messages to the
tests where error
Just to follow up on this, yes, it was an include path thing.
On Mar 24, 2005, at 7:33 PM, Tom Lane wrote:
Ben <[EMAIL PROTECTED]> writes:
I'm trying to build 8.0.1 on OS X, and after a simple ./configure
without any options, the build progresses smoothly until, when
building
pg_ctl:
pg_ctl.c: In
Well, 33 years from now, it's a pretty safe bet that this project won't
exist. :) Or, if it does exist, that it will have been rewritten from
scratch for numerous other reasons.
(I know, I know, and 640KB ought to be enough memory for everybody.
but this time I'm right.)
On Mar 26, 2005, a
Bricklen Anderson <[EMAIL PROTECTED]> writes:
>> Once I recompile the function, I no longer get that message. Is there
>> anything else that I can check or do to make this stop happening? Or is
>> this a sign of things to come (possible corruption, etc?)
Well, the original error sounds like a di
The way our app is structured, storing unixtime is the most efficient
way to get what we want.
I can't recall why I started using abstime... I started it with some
other projects years ago and was under the impression that it was the
preferred way. Maybe it was then, but isn't anymore? Maybe I'
Ben <[EMAIL PROTECTED]> writes:
> Is there a workaround I could use,
Make the column abstime instead of int, perhaps. Or better yet
timestamp. Have you considered what will happen in 2038?
regards, tom lane
---(end of broadcast)--
Bricklen Anderson wrote:
Hi listers!
I'll start with some details:
select version();
PostgreSQL 8.0.0 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.5
(Debian 1:3.3.3-5)
Upon compiling a new function that I was working on, I came across an
error:
"could not read block 0 of relation 1663/172
On Sat, Mar 26, 2005 at 12:22:51PM -0800, Ben wrote:
>
> Is there a workaround I could use, or should I stick with 7.4 for now?
The documentation discourages using abstime -- is there a reason
you're using it instead of extract(epoch from now())? That should
work in the query.
Is there a reason
Hi listers!
I'll start with some details:
select version();
PostgreSQL 8.0.0 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.5 (Debian
1:3.3.3-5)
Upon compiling a new function that I was working on, I came across an error:
"could not read block 0 of relation 1663/17239/16709: Bad address" whi
Is there a workaround I could use, or should I stick with 7.4 for now?
On Mar 26, 2005, at 11:14 AM, Tom Lane wrote:
Michael Fuhr <[EMAIL PROTECTED]> writes:
SELECT x FROM foo WHERE x < now()::abstime::integer;
ERROR: unsupported type: 23
It looks like examine_variable shouldn't be throwing away t
Michael Fuhr <[EMAIL PROTECTED]> writes:
> SELECT x FROM foo WHERE x < now()::abstime::integer;
> ERROR: unsupported type: 23
It looks like examine_variable shouldn't be throwing away the
RelabelType on the now() call ... this code is all new in 8.0
IIRC, which is why you don't see the failure in
On Sat, Mar 26, 2005 at 10:24:06AM -0700, Michael Fuhr wrote:
>
> SELECT x FROM foo WHERE x < now()::abstime::integer;
> ERROR: unsupported type: 23
\set VERBOSITY verbose
SELECT x FROM foo WHERE x < now()::abstime::integer;
ERROR: XX000: unsupported type: 23
LOCATION: convert_timevalue_to_sca
On Sat, Mar 26, 2005 at 08:25:24AM -0800, Ben wrote:
>
> gr-test=> select expires from invitecodes where expires <
> ((now())::abstime)::int4;
> ERROR: unsupported type: 23
Hmmm...
CREATE TABLE foo (x integer);
INSERT INTO foo (x) VALUES (10);
INSERT INTO foo (x) VALUES (20);
I'm attempting to upgrade to 8.0.1, and have hit my latest hurdle: an
unsupported type when I try to compare ints. Example:
gr-test=> \d invitecodes
Table "public.invitecodes"
Column | Type |Modifiers
+-
+---
On Mar 25, 2005, at 6:16 PM, OpenMacNews wrote:
if i were to consider 'storing' those messages trees, instead, in a
pgsql db, i i mmediately/naively think of three possible options
(a) simple DB-stored references to flat file:/// locations
(b) pointers to external, actionable (parseable? writeabl
44 matches
Mail list logo
