Skip site navigation (1) Skip section navigation (2)

Re: domain constraints and UNKNOWN params

From: Neil Conway <neilc(at)samurai(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches <pgsql-patches(at)postgresql(dot)org>, david(at)justatheory(dot)com
Subject: Re: domain constraints and UNKNOWN params
Date: 2006-01-12 05:28:40
Message-ID: 1137043720.9143.123.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
On Wed, 2006-01-11 at 23:31 -0500, Tom Lane wrote:
> This is a good catch, but the patch's added check on targetTyptype is a
> waste of code and cycles.  coerce_to_domain is perfectly capable of
> doing nothing when nothing is called for.

Ah, right. Attached is a corrected patch.

> I wonder whether there is any reasonably simple way to audit the whole
> backend for missing domain processing...

Yeah, I've been thinking along the same lines -- the recent spate of
issues doesn't give me a lot of confidence in the correctness or
completeness of the current implementation. I don't really see a way to
check the code that doesn't require a fair amount of manual auditing,


Attachment: unknown_prep_stmt_domain-2.patch
Description: text/x-patch (728 bytes)

In response to


pgsql-patches by date

Next:From: Tom LaneDate: 2006-01-12 05:45:56
Subject: Re: domain constraints and UNKNOWN params
Previous:From: ITAGAKI TakahiroDate: 2006-01-12 05:22:41
Subject: Re: Free WAL caches on switching segments

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group