Sorry but I made a mistake in describing the problem.
PQfmod(...) returns 20 + 4, but strlen(PQgetvalue(...)) returns
something varying, more than 24.
Since you said atttypmod is char len + 4, "The actual physical length in
bytes of a column entry might be more", it's dependant to the current
loc
On Tue, 2003-02-25 at 22:08, Tim Ellis wrote:
> On Mon, 2003-02-24 at 23:03, Oliver Elphick wrote:
> > different for different countries. There was a discussion of this on
> > the patches list recently
> > (http://archives.postgresql.org/pgsql-patches/2003-02/msg00038.php and
> > the surrounding t
On Mon, 2003-02-24 at 22:59, Robert Treat wrote:
> [EMAIL PROTECTED] rms_db]$ cal 9 1752
>September 1752
> Su Mo Tu We Th Fr Sa
>1 2 14 15 16
> 17 18 19 20 21 22 23
> 24 25 26 27 28 29 30
>
> I guess adding 1 day to 1752-09-02 should give us 1752-09-14, but your
> right, it gives us
[EMAIL PROTECTED] writes:
> We have a postgres backend to our Mail Server product, and encountering
> performance issues. Simple selects are taking 7-10 seconds..
strace is not a particularly useful level of analysis for Postgres
performance problems. I'd suggest looking at your database schem
