tgname munged

From: <gnuoytr(at)rcn(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: tgname munged
Date: 2010-08-04 15:30:21
Message-ID: 20100804113021.AGI17555@ms14.lnh.mail.rcn.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Can anyone explain why the following query (used by AQT to display its tree):

SELECT trig.tgname,
tab.relname,
case trig.tgenabled
when '1' then 'yes'
else 'no'
end,
trig.oid
FROM pg_catalog.pg_trigger trig,
pg_catalog.pg_class tab,
pg_catalog.pg_namespace nam
WHERE trig.tgrelid=tab.oid
AND tab.relnamespace=nam.oid
AND nam.nspname ='public' -- ?
ORDER BY 1

produces tgname like (from memory) RIFKConstraint...<number>
while without the ORDER BY (and it doesn't matter how you identify the column) tgname displays correctly (well, the same as what you see if you SELECT * FROM pg_trigger).

thanks,
Robert

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jay Flattery 2010-08-04 15:41:38 Re: hashtable issue - HASH_FIND??
Previous Message Merlin Moncure 2010-08-04 15:12:15 Re: Danger of idiomatic plpgsql loop for merging data