pg_dump: Add ExecuteSqlCopy and simplify ExecuteSqlQuery - Mailing list pgsql-hackers

From Corey Huinker
Subject pg_dump: Add ExecuteSqlCopy and simplify ExecuteSqlQuery
Date
Msg-id CADkLM=dvKHrt864audavQXB-yATV_4Vj+Qo_AgFhtv0ka2xdLQ@mail.gmail.com
Whole thread Raw
List pgsql-hackers
The thread about tablecmds.c being too large for some code inspection tooling got me thinking about ways to improve the second worst offender: pg_dump.c.

Those investigations of mine haven't yet revealed a way to split the file that I find effective, let alone helpful. However, it has shown me a few patterns within pg_dump.c that I'm proposing to change.

Of the current 84 calls to the convenience routine ExecuteSqlQuery(), 83 of them are regular queries which expect a result of PGRES_TUPLES_OK. The other one expects PGRES_COPY_OUT. So it seems worthwhile to remove the parameter entirely and assume the caller wants PGRES_TUPLES_OK. For the one exception, ExecuteSqlCopy() is created, though one could argue that we might just do without the convenience routine altogether. Patch attached.
Attachment

pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Remaining dependency on setlocale()
Next
From: Nathan Bossart
Date:
Subject: Re: [PATCH] Fix ARM64/MSVC atomic memory ordering issues on Win11 by adding explicit DMB ?barriers