| From: | "Sergey E(dot) Koposov" <math(at)sai(dot)msu(dot)ru> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Strange RETURN NEXT behaviour in Postgres 8.0 |
| Date: | 2005-02-16 21:28:41 |
| Message-ID: | Pine.LNX.4.44.0502170023550.14831-100000@lnfm1.sai.msu.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 16 Feb 2005, Richard Huxton wrote:
> This is just a shot in the dark, but I don't suppose you've dropped or
> modified any columns in "usno" have you?
>
> I seem to remember some subtle problems with dropped columns and plpgsql
> functions - could be one of those still left. It'd look like tablesize
> was the problem because of course no-one's got time to test with 500
> million test rows.
1) I have static tables. I dont modify them!
2) My test table is q3c (with 2 rows), and the table with 500 millions of
rows is not test table, it is the table with data :-)
> --
> Richard Huxton
> Archonet Ltd
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2005-02-16 21:35:01 | Re: Help me recovering data |
| Previous Message | Richard Huxton | 2005-02-16 21:22:20 | Re: Strange RETURN NEXT behaviour in Postgres 8.0 |