Re: [Solved] SQL Server to PostgreSQL - Mailing list pgsql-general

From Bruce Momjian
Subject Re: [Solved] SQL Server to PostgreSQL
Date
Msg-id 200010150328.XAA22369@candle.pha.pa.us
Whole thread Raw
In response to Re: [Solved] SQL Server to PostgreSQL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
[ Charset ISO-8859-1 unsupported, converting... ]
> Ian Turner <vectro@pipeline.com> writes:
> > Don't variable-length records incur a performance overhead?
>
> Only to the extent that the system can't cache offset information for
> later columns in that table.  While someone evidently once thought that
> was worthwhile, I've never seen the column-access code show up as a
> particularly hot spot in any profile I've run.  I doubt you could
> actually measure any difference, let alone show it to be important
> enough to be worth worrying about.

It clearly is a hot-spot.  That monster macro, fastgetattr(), in
heapam.h is in there for a reason. It accounts for about 5% for straight
sequential scan case, last I heard from someone who ran a test.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-general by date:

Previous
From: Collin Peters
Date:
Subject: JDBC Driver homepage down
Next
From: Bruce Momjian
Date:
Subject: Re: [Solved] SQL Server to PostgreSQL