| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, David Fetter <david(at)fetter(dot)org>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Why is pq_begintypsend so slow? |
| Date: | 2020-05-18 18:08:53 |
| Message-ID: | 2879.1589825333@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> writes:
> Again, I see problems with the types declared in Postgres.
> 1. pq_sendint32 (StringInfo buf, uint32 i)
> 2. extern void pq_sendbytes (StringInfo buf, const char * data, int
> datalen);
We could spend the next ten years cleaning up minor discrepancies
like that, and have nothing much to show for the work.
> To avoid converting from (int) to (uint32), even if afterwards there is a
> conversion from (uint32) to (int)?
You do realize that that conversion costs nothing?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-05-18 18:26:55 | Re: Two fsync related performance issues? |
| Previous Message | Tom Lane | 2020-05-18 17:57:19 | Re: fill_extraUpdatedCols is done in completely the wrong place |