I should point out that the bug I reported about dependencies and
changing the type of a serial column still exists.
Once you change a serial column to something else, you cannot ever
change the default IIRC...
Chris
Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
On Tue, 2
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Tue, 2 Aug 2005, Tom Lane wrote:
>> Well, that second line is *definitely* a SERIAL column linkage.
>>
>> Is it possible they did "create table xa_url(id bigserial, ...)" and
>> then later changed the default expression for the column?
> 'k, am c
On Tue, 2 Aug 2005, Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
On Tue, 2 Aug 2005, Tom Lane wrote:
Hmm, odd. But maybe there are traces of a SERIAL linkage? What do
you get from
select * from pg_depend where objid = 'xa_url_id_seq'::regclass;
# select * from pg_depend
Dennis Bjorklund wrote:
> On Tue, 2 Aug 2005, Jeff Davis wrote:
>
>
Does the SQL standard provide no way to have a NULL character in a
string constant? Is single-quote the only special character?
>>>
>>>I don't think it forbids you from using the null character. It's not like
>>>the stri
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Tue, 2 Aug 2005, Tom Lane wrote:
>> Hmm, odd. But maybe there are traces of a SERIAL linkage? What do
>> you get from
>>
>> select * from pg_depend where objid = 'xa_url_id_seq'::regclass;
> # select * from pg_depend where objid = 'xa_url_id_s
On Tue, 2 Aug 2005, Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
On Tue, 2 Aug 2005, Tom Lane wrote:
Given the name, this could be a SERIAL column's sequence --- which is
not dumped as a separate object by pg_dump, since recreating the SERIAL
column ought to create it.
One
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Tue, 2 Aug 2005, Tom Lane wrote:
>> Given the name, this could be a SERIAL column's sequence --- which is
>> not dumped as a separate object by pg_dump, since recreating the SERIAL
>> column ought to create it.
> One of their functions does an in
On Tue, 2 Aug 2005, Tom Lane wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
Have databse that \ds shows several sequences, but one in partiicular, I
can't seem to 'dump' with pg_dump:
public | xa_url_id_seq | sequence | pareto_su
Given the name, this could be a S
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Have databse that \ds shows several sequences, but one in partiicular, I
> can't seem to 'dump' with pg_dump:
> public | xa_url_id_seq | sequence | pareto_su
Given the name, this could be a SERIAL column's sequence --- which is
I've started scaling dbt3 up to the 10GB scale factor against CVS and
the fast COPY patch:
http://www.testing.osdl.org/projects/dbt3testing/results/dev4-010/53/
I'm sure there are some better database parameters I should use so
please let me know what to try. ;) What I've found interesting is th
"Thomas F. O'Connell" <[EMAIL PROTECTED]> writes:
> Tom seems to come pretty close to a TODO item in his analysis in my
> opinion. Something like:
> "Make the planner ignore temp tables of other backends when expanding
> an inheritance list."
I've done this in CVS tip. I'm not sure whether i
I had posted this earlier, but had insufficient info (or access) to
provide much detail ... now, I've got the access, and this really isn't
making much sense ...
Have databse that \ds shows several sequences, but one in partiicular, I
can't seem to 'dump' with pg_dump:
public | xa_url_id_
For the past 11 months or so[1], I've been working full-time on
PostgreSQL as an employee of Fujitsu Australia Software Technology. I'm
grateful to Fujitsu for giving me this opportunity, and I've enjoyed the
past year. However, I'm returning to university in the fall, and
therefore I will no l
Great! Is background writer clogging worthy? That's the one that put
postgres in a nearly unusable state after this bug was tripped.
Thanks!
--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
Strategic Open Source: Open Your i™
http://www.sitening.com/
110 30th Avenue Nor
On Tue, 2 Aug 2005, Jeff Davis wrote:
> >>Does the SQL standard provide no way to have a NULL character in a
> >>string constant? Is single-quote the only special character?
> >
> > I don't think it forbids you from using the null character. It's not like
> > the strings are zero terminated. Som
Dennis Bjorklund wrote:
> On Mon, 1 Aug 2005, Jeff Davis wrote:
>
>
>>Does the SQL standard provide no way to have a NULL character in a
>>string constant? Is single-quote the only special character?
>
>
> I don't think it forbids you from using the null character. It's not like
> the strings
On Mon, 1 Aug 2005, Jeff Davis wrote:
> Does the SQL standard provide no way to have a NULL character in a
> string constant? Is single-quote the only special character?
I don't think it forbids you from using the null character. It's not like
the strings are zero terminated. Some encodings migh
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: 02 August 2005 05:55
> To: Jeff MacDonald
> Cc: Matthew T. O'Connor; [EMAIL PROTECTED];
> pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Autovacuum to-do list
>
On Tue, Aug 02, 2005 at 08:25:00AM +0100, Dave Page wrote:
[..snipped..]
> >
> > Oooo... That's a lot of win32 ignorance to ignore... :-)
> >
> > Push control-alt-delete and look under "Performance". I believe
> > Windows may even keep *more* information that Linux. It's all a
> > question of fig
19 matches
Mail list logo
