pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: bert.horvath@fh-erfurt.de
Cc: pgsql-interfaces@postgresql.org
Subject: Re: C-Interface Amound of Tupels in Result after COPYout
Date: Thu, 15 Nov 2007 10:27:00 -0500
Message-ID: <2564.1195140420@sss.pgh.pa.us> (raw)
In-Reply-To: <473C3851.6060300@fh-erfurt.de>
References: <473C3851.6060300@fh-erfurt.de>

Bert Horvath <bert.horvath@fh-erfurt.de> writes:
> do i have any chance to get the amount of tupels in the result set after 
>    executing a query with a copy command? Its not a problem to count the 
> columns with PQnFields(*conn,*result) but there is no documentation für 
> PQnTupels(*conn,*result) and it does not work.

PQcmdTuples.  PQnTuples is for the number of rows actually returned to
the client by a SELECT.

			regards, tom lane



view thread (5+ messages)  latest in thread

Message-ID: <2564.1195140420@sss.pgh.pa.us>
Permalink:  ../2564.1195140420@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2564.1195140420@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: tgl@sss.pgh.pa.us, bert.horvath@fh-erfurt.de
  Subject: Re: C-Interface Amound of Tupels in Result after COPYout
  In-Reply-To: <2564.1195140420@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox