From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: vacuum and row type |
Date: | 2011-06-02 16:24:54 |
Message-ID: | 4DE7B956.1010803@sigaev.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I think we could just let this code assume success for type RECORD. It
> won't affect VACUUM/ANALYZE, since there are (for reasons that should
> now be obvious) no table or index columns of anonymous composite types.
Of course, it's impossible to store anonymous composite type anywhere, but
we still have possibility to use it in ORDER BY at least, following query works
on HEAD but fails with patch:
select ROW(1, n) as r from generate_series(1,5) as n order by r;
> What I was thinking last night is that it'd be smart to move all this
> logic into the typcache, instead of repeating all the work each time we
Agree
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-06-02 16:29:44 | Re: Please test peer (socket ident) auth on *BSD |
Previous Message | Andrew Dunstan | 2011-06-02 16:20:53 | Re: Please test peer (socket ident) auth on *BSD |