Hi Daniel,
Maybe make procedural wrappers around all events undertaken and simulate it?
ie:
1. Client connects to MS SQL Server (Application Server) and PG Server
2. SQL Server connects to PG Server aswell
3. Client begins new record process
4. New record process starts by putting PG into
and the
server) should commit or rollback now
So both Postgres-Connections has to be @ the same TransAction-OID in
Postgres.
greets
Daniel
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Jason
Godden
Gesendet: Donnerstag, 17. Juli 2003
Hi Brice,
Thats very wrong...
Whilst changing conf settings will speed things up it still shouldn't affect
loading a 32mb dump file. Have you tried restarting PG with logging and then
piping the dump file through psql? You should find that you get a lot more
direct feedback from psql. This
Whilst I agree with what Bruno said regarding adding a default option to the
copy syntax I think that the basic principles Stephan and I outlined in how
copy treats your import is correct and the developers did the right thing.
Now if the devs, you or I want to add a default option to copy in
create table import_contact (
id character(7) not null primary key,
fm character(30),
ls character(30),
addr character(30),
city character(25),
st character(2),
c character(1),
start decimal(6),
end decimal(6),
) WITHOUT OIDS;
cat datafile.dat | psql -dthedatabase -c copy import_contact from
import_contact; | psql -dthedatabase
Rgds,
Jason
On Sat, 16 Aug 2003 01:10 pm, expect wrote:
On Sat, 16 Aug 2003 09:33:51 +1000
Jason Godden [EMAIL PROTECTED] wrote:
Ahh, thanks for this. And thanks to all the others that helped me on my
way. Hopefully I'll be able to give something back
-Original Message-
From: Jason Godden
To: [EMAIL PROTECTED]
Sent: 8/15/2003 7:33 PM
Subject: Re: [GENERAL] summary and request
create table import_contact (
id character(7) not null primary key,
fm character(30),
ls character(30),
addr character(30),
city character(25),
st character
Hi Sean,
Yeah - It is declared VOLATILE. I think there must be something specific with
the way PL/PGSQL handles child processes of a called function. The child
process actually spawns mpg123 or ogg123 so it has to live beyond the life of
the parent. Not sure. What I might do is rewrite the
to decoder info
and everything purrs.. sigh. Writing help requests to the list when you've
only exhausted half the possibilities are a bit silly.
Thanks for your time,
Jason
On Mon, 18 Aug 2003 11:41 pm, Jan Wieck wrote:
Jason Godden wrote:
Hi Sean,
Yeah - It is declared VOLATILE. I think
Hi Philip,
Pg is more ansi compliant than most (GoodThing (TM)). You can use the 'when'
conditional but not to do what you need. If I understand you correclty you
should be able to acheive the same result using two seperate queries and the
(NOT) EXISTS or (NOT) IN clause. Failing that have
A trigger is the right way. Rules rewrite a statement whereas triggers are at
row level.
so in plpgsql:
create or replace function trig_param_ins_upd() returns trigger as '
begin
new.ts = current_timestamp;
return new;
end;' language 'plpgsql';
create trigger
Hi David,
I'd say that if it is a new app develop it with 7.4 and use statement level
triggers otherwise you could use normal triggers and perform a count each
time but that will slow things down dramatically.
Other option is to use cron and write a daemon/script to periodically check
the
Hi Tom,
Thanks for the fast response. One learns something new everyday!
Cheers,
Jason
On Tue, 7 Oct 2003 12:14 am, Tom Lane wrote:
Jason Godden [EMAIL PROTECTED] writes:
I'm in the process of moving a rather complicated plpgsql stored
procedure to a C module and I'm curious about how
On Sun, 21 Dec 2003 12:05 am, Shridhar Daithankar wrote:
Does it mean mysql got stored procedures? Wow..
I would like to see details but since I don't know much details about
either mysql or java, I can not describe it.
Can anybody give a summary as in how much it takes mysql as far as
14 matches
Mail list logo
