Applied by Tom Lane. Thanks.
---
Volkan YAZICI wrote:
> On Feb 11 11:24, Bruce Momjian wrote:
> > I have updated the patch to match CVS (attached), but am seeing the
> > following regression differences where the COPY error
On Feb 11 11:24, Bruce Momjian wrote:
> I have updated the patch to match CVS (attached), but am seeing the
> following regression differences where the COPY error messages are now
> missing.
I've revised the patch (attached) and now it seems to be ok - passes
regression tests too. Any other comme
Volkan YAZICI wrote:
> Here's a new try. This one touches to pg_dump side too - for v3
> COPY functions usage instead of deprecated ones.
>
> I'd be so appreciated if somebody can review attached patch.
I have updated the patch to match CVS (attached), but am seeing the
following regression diffe
I've just realized an exception in the sending data while using
PQsendCopyData(). Function's blocking behaviour is not guaranteed,
therefore a
if (PQisnonblocking())
PQsetnonblocking(conn, 0)
kind of phrase required before using PQsendCopyData(). But after a
small investig
Here's a new try. This one touches to pg_dump side too - for v3
COPY functions usage instead of deprecated ones.
I'd be so appreciated if somebody can review attached patch.
Regards.
Index: src/backend/commands/copy.c
===
RCS file:
On Dec 22 01:52, Tom Lane wrote:
> > ! {
> > ! uint64processed = DoCopy((CopyStmt *) parsetree);
> > ! charbuf[21];
> > !
> > ! snprintf(buf, sizeof(buf), UINT64_FORMAT, processed);
> > ! snprintf(completionTag, CO
Volkan YAZICI <[EMAIL PROTECTED]> writes:
> I tried to prepare a patch for these TODO items:
> - Have COPY return the number of rows loaded/unloaded?
> - Update [pg_dump and] psql to use the new COPY libpq API.
> ! cstate->raw_buf_index = cstate->raw_buf_len = 0;
> ! cstate->raw_buf_inde
Volkan YAZICI wrote:
I tried to prepare a patch for these TODO items:
- Have COPY return the number of rows loaded/unloaded?
- Update [pg_dump and] psql to use the new COPY libpq API.
I'll apply this today or tomorrow, barring any objections.
BTW, if we're using an int64 counter for the # of
I tried to prepare a patch for these TODO items:
- Have COPY return the number of rows loaded/unloaded?
- Update [pg_dump and] psql to use the new COPY libpq API.
Added an "uint64 processed" to "struct CopyStateData". It's
incremented each time on a tuple send/receive made by
CopyTo/CopyFrom. Co
