Title: Corrupt catalog
In trying to determine why I had a corrupted piece of data (still investigating that) I created a temporary table that contained the row of data in question. In doing so, I must have done something to the pg_catalog because I no longer was able to perform a dump
Dave Page dpage@vale-housing.co.uk writes
It occurs to me that there is no longer any great need to have a
separate hackers list for win32 development. Perhaps we should close it
down now and keep all development on -hackers?
I agree with it.
Regards, Dave.
---(end
It occurs to me that there is no longer any great need to
have a separate hackers list for win32 development. Perhaps
we should close it down now and keep all development on -hackers?
I also think this is a good idea. The number of win32 only issues of
-hacker level is significantly smaller
I thought we'd more or less dropped that idea based on Andreas'
responses.
I've heard no argument against renaming
pg_complete_relation_size() to
pg_total_relation_size()
Having spent days, no, weeks deciding on that name on list I
do not want to see it change this late,
I am trying to write a C trigger. Essentially
TriggerData *in = (TriggerData *) fcinfo-context;
HeapTupleHeader tuple=in-tg_trigtuple-t_data;
Datum datum;
datum = GetAttributeByName(tuple, unit_id, isnull);
and that last line fails with
ERROR: cache lookup failed for type
Patrick Welche [EMAIL PROTECTED] writes:
I am trying to write a C trigger. Essentially
TriggerData *in = (TriggerData *) fcinfo-context;
HeapTupleHeader tuple=in-tg_trigtuple-t_data;
Datum datum;
datum = GetAttributeByName(tuple, unit_id, isnull);
and that last line
Magnus Hagander wrote:
I thought we'd more or less dropped that idea based on Andreas'
responses.
I've heard no argument against renaming
pg_complete_relation_size() to
pg_total_relation_size()
Having spent days, no, weeks deciding on that name on list I
do not want to see it change
Having spent days, no, weeks deciding on that name on list I do not
want to see it change this late, especially as we'll now need to go
and update pgAdmin again!
Fortunately, pgAdmin doesn't use that function, but only the
basic pg_relation_size(). Phew!
Good for you :-)
Also, the
On Sat, 2005-17-09 at 14:47 +0200, Magnus Hagander wrote:
Also, the change to pg_cancel_backend breaks backwards compatibility
with 8.0, which is a whole lot worse than breaking it with 8.1-beta1.
Yeah, I thought about that (and Bruce and I already discussed it offlist
before I committed the
