Joe Conway <[EMAIL PROTECTED]> writes:
> I have thought before that we were overloading fn_extra a bit too much.
> Is there any merit in having more than one "extra" member in FmgrInfo
> going forward?
Not sure what --- how would you decide which to use, and what stops
there being a conflict on
"Chris Hutchinson" <[EMAIL PROTECTED]> writes:
> pg_dump -t includes SERIAL column sequence details for the dumped table when
> the table has been created in v8 postgresql.
> Tables migrated from an earlier pg version aren't being dumped with their
> sequence details. (These tables were created in
Tom Lane wrote:
"Ezequiel Tolnay" <[EMAIL PROTECTED]> writes:
I've created the cardnumber_t datatype, which is an int8, to provide
implicit typecasting with varchar padding the result with zeroes.
Conversions work as expected between int4, int8, cardnumber_t and varchar.
They also work fine between
Andreas Lange <[EMAIL PROTECTED]> writes:
> Our upgrade from 7.4.6 to 8.0.1 only had one small glitch. Two tables
> got dumped in the wrong order (before their dependecies) and had to get
> their contents added manually after the restore. I've atleast isolated
> the part where things go wrong.
"Ezequiel Tolnay" <[EMAIL PROTECTED]> writes:
> I've created the cardnumber_t datatype, which is an int8, to provide
> implicit typecasting with varchar padding the result with zeroes.
> Conversions work as expected between int4, int8, cardnumber_t and varchar.
> They also work fine between int4[],
I wrote:
> ... Maybe we could
> put in a hack that detects whether a table has yet been vacuumed, and
> sets 10/1000 as the minimum stats --- not fixed values, but minimum
> values that can be overridden when the table is actually larger ---
> until it has been vacuumed.
For lack of any better s
Bruce Momjian writes:
> Agreed. What is really weird is that the time is always displayed for a
> zero value:
> test=> select interval '0 years' year;
>interval
> --
>00:00:00
> (1 row)
> but a non-zero shows the proper units:
> test=> se
Tom Lane wrote:
> Roy Badami <[EMAIL PROTECTED]> writes:
> > test=> select interval '1 hour 1 minute';
> > interval
> > --
> > 01:01:00
> > (1 row)
>
> > Hmm, I don't think I really like having a seconds field in the output,
> > given that the column is by definition
Roy Badami <[EMAIL PROTECTED]> writes:
> test=> select interval '1 hour 1 minute';
>interval
> --
>01:01:00
> (1 row)
> Hmm, I don't think I really like having a seconds field in the output,
> given that the column is by definition only storing data to a
>
test=> select interval '1 hour 1 minute';
interval
--
01:01:00
(1 row)
Hmm, I don't think I really like having a seconds field in the output,
given that the column is by definition only storing data to a
precision of a minute.
On 2005-03-23, Tom Lane <[EMAIL PROTECTED]> wrote:
> No, it wouldn't, because by the time you do the first FK trigger you'd
> have one row/one page in the referenced table, so it'd still look like a
> seqscan situation to the planner. The only way we could make that work
> is to effectively disabl
11 matches
Mail list logo
