Hi Steve,
Your question about - pg_proc
select t.typname from pg_type t , pg_proc p
where p.proname = '' and p.proargtypes[0] = t.oid ;
select t.typname from pg_type t , pg_proc p
where p.proname = '' and p.proargtypes[1] = t.oid ;
...
select t.typname from pg_type t , pg_proc p
where p.pronam
Hi,
I've done some research on your request,
but I could not find very much to help you.
What I've found about
1) Connections
http://www.postgresql.org/idocs/index.php?runtime-config.html
enable LOG_CONNECTIONS (boolean), LOG_PID (boolean)
to log database users
2) Table locks
nothing
3) C
Hi,
I've seen no answer to your question within four days.
Have you solved it on your own?
I'm interested in the stuff you asked for, too.
Please let me know about the status of the function.
If you haven't got any answer, maybe we should try to get
one using a clearer mail subject.
Regards
[HACKERS] What executes faster?
Now that I've found the solution for my duplicate key problem,
I'm wondering what executes faster when I have to check for
duplicates.
1. try to update
if no row affected -> do the insert
else done
2. do a select
if row not found -> do the inse
Thanks a lot. Now that I've read your message,
I wonder why I was asking something trivial.
Christoph
> > In a C application I want to run several
> > insert commands within a chained transaction
> > (for faster execution).
> > >From time to time there will be an insert command
> > causing an
>
Hi all,
Sorry for bothering you with my stuff for the second time
but I haven't got any answer within two days and the problem
appears fundamental, at least to me.
I have a C application running to deal with meteorological data
like temperature, precipitation, wind speed, wind direction, ...
In a C application I want to run several
insert commands within a chained transaction
(for faster execution).
>From time to time there will be an insert command
causing an
ERROR: Cannot insert a duplicate key into a unique index
As a result, the whole transaction is aborted and all
the pre
[HACKERS] Where are the ERROR: Messages
I'm converting from a C based program
to PostgreSQL. There are some DBMS
specific errors caught, i.e. deadlocks.
Not only for this reason, but also from
general curiosity I'd like to know what
kinds of ERRORS PostgreSQL is dealing with.
Which source c
Within psql
examine the system tables
pg_proc
pg_trigger
Refer to the documentation
Chapter System Catalogs
Regards, Christoph
PS
I was sending this mail yesterday
to '[EMAIL PROTECTED]'
but it seemed to disappear,
at least I did not get it back.
Has anybody experienced similar effects
I agree.
This mailing list is not a forum to express
aversions to other software products,
no matter how justified these aversions are.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/
Have a look into the system tables
pg_proc
pg_trigger
Have a look into the documentation,
refer to System Catalogs
Within psql you get
System Catalogs listed by \dS
specific information about a table
by i. e. \d pg_proc
Regards, Christoph
---(end of broadcast)-
Adam,
try this
select distinct job_num, count (job_num) from search_record
group by job_num ;
don't worry about an ordered list - group by does it for you.
Regards, Christoph
>
> HACKERS: see the end of this message about a possible optimisation for
> ORDER BY+LIMIT cases (the normal use o
[HACKERS] ERROR: Cannot insert a duplicate key into a unique index
I'm working on a C code application using loads of
insert commands.
It is essential to distinguish between an error
coming from a misformed command or other fatal
reasons and a duplicate key.
In either case, the PQresultStat
13 matches
Mail list logo
