> postgresql.org cvsup repository is broken (and according to my records,
> been so for last 4 days at least). Unfortunately, I can't get my changes
> in correct format unless that gets fixed...So I guess that'll go in 7.3 :(
The beta release schedule is on hold until we can get access. I've
wast
Do the multibyte regression tests in src/test/mb currently pass for
other people? I'm getting failures on most of them, and what it looks
like to me is that the latest commits of the "expected" files contain
wrong results.
regards, tom lane
---(en
On Thu, 20 Sep 2001, Alex Pilosov wrote:
> CVS repository also seems broken right now, I'm unable to log in (cvs
> login: authorization failed: server cvs.postgresql.org rejected access
> to /home/projects/pgsql/cvsroot for user anoncvs) in both
> cvs.postgresql.org and anoncvs.postgresql.org wit
On Mon, 17 Sep 2001, Tom Lane wrote:
> Alex Pilosov <[EMAIL PROTECTED]> writes:
> > Attached patch does the above.
>
> Alex, could we have this resubmitted in "diff -c" format? Plain diff
> format is way too risky to apply.
Tom,
postgresql.org cvsup repository is broken (and according to my re
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Had you actually done anything to the database between postmaster
>> startup and kill?
> I've run the regression tests several times (parallel and serial) and
> killed the postmaster at different places, even killed a few backends
Tom Lane writes:
> Had you actually done anything to the database between postmaster
> startup and kill?
I've run the regression tests several times (parallel and serial) and
killed the postmaster at different places, even killed a few backends in
between, actual redo happened, yet shutdown was
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> Huh? If you zap the postmaster with kill -9, the last checkpoint record
>> in the WAL log will not have the shutdown bit set.
> It does here:
Had you actually done anything to the database between postmaster
startup and kill? I
Tom Lane writes:
> Huh? If you zap the postmaster with kill -9, the last checkpoint record
> in the WAL log will not have the shutdown bit set.
It does here:
peter ~$ pg-install/bin/postmaster -D pg-install/var/data
DEBUG: database system was shut down at 2001-09-20 18:52:58 CEST
DEBUG: chec
Not sure how to do this, but it shouldn't be too ugly. I want to drop
columns from a table as well as be able to change the data type of a column.
Where should I be looking in the source for altering tables? For removing I
don't imagine it could be too ugly as all it should be is a reverse add.
Tom Lane writes:
> It means the latest checkpoint record in the WAL log has the shutdown bit
> set, implying that there was an intentional shutdown.
I'd hardly consider a kill -9 an intentional shutdown. ???
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> It means the latest checkpoint record in the WAL log has the shutdown bit
>> set, implying that there was an intentional shutdown.
> I'd hardly consider a kill -9 an intentional shutdown. ???
Huh? If you zap the postmaster with
I'm trying to update my cvs tree and am currently seeing the following:
Parsing supfile "postgres.cvsup"
Connecting to cvsup.postgresql.org
Cannot connect to cvsup.postgresql.org: Connection refused
Will retry at 20:15:50
Is this expected? Should cvsup.postgresql.org be answering connection
requ
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> When the server starts I see something like
> DEBUG: redo record is at 0/146ED4; undo record is at 0/0; shutdown TRUE
> but what does "shutdown TRUE" mean? It doesn't mean "I'm shutting down"
> nor "the last shutdown was successful", so it's not ve
On Thu, 20 Sep 2001, Lamar Owen wrote:
> On Thursday 20 September 2001 08:58 am, mlw wrote:
> > Now that GreatBridge is gone. (I'm pretty sad about that, they looked like
> > they were working on some cool stuff.)
>
> > Has this changed, in any way, the development path of PostgreSQL?
>
> Just my
On Thursday 20 September 2001 12:47 pm, Marc G. Fournier wrote:
> On Thu, 20 Sep 2001, Lamar Owen wrote:
> > On Thursday 20 September 2001 08:58 am, mlw wrote:
> > > Has this changed, in any way, the development path of PostgreSQL?
> > Just my personal opinion:
> > long before Great Bridge was on
When will CVSup be upgraded? I continue to see
that you have the time bug. I just ran cvsup and got:
Parsing supfile "cvsup_config"
Connecting to postgresql.org
Connected to postgresql.org
Server software version: REL_16_1
Server postgresql.org has the S1G bug
See http://www.polstra.com/project
When the server starts I see something like
DEBUG: redo record is at 0/146ED4; undo record is at 0/0; shutdown TRUE
but what does "shutdown TRUE" mean? It doesn't mean "I'm shutting down"
nor "the last shutdown was successful", so it's not very obvious.
--
Peter Eisentraut [EMAIL PROTECTED
On Thursday 20 September 2001 11:04 am, Thomas Lockhart wrote:
> > ... but PostgreSQL cannot be orphaned in that
> > sense due to its open source nature.
> I'll second that. It isn't just "the open source nature" of PostgreSQL
> which will keep it viable, it is the active developer and user commu
OK, I see a patch from 2001-09-10 for parse_target.c which is a smoking
gun. The patch tries to force a column name for the TypeCast node, and
doesn't check to see if one was actually specified :(
So that probably explains why, on my system,
select cast(int4 '1' as float8);
fails, while
se
> ... but PostgreSQL cannot be orphaned in that
> sense due to its open source nature.
I'll second that. It isn't just "the open source nature" of PostgreSQL
which will keep it viable, it is the active developer and user community
which has grown up around it which makes it unlikely that it will
> Nope, these variants all work for me. But I know where the problem is
> now: you have a broken version of FigureColname() in parse_target.c.
> Somebody submitted a bogus patch last week; I've fixed it in current
> CVS, but evidently your sources are from last week.
Sure. cvsup needed to be upg
On Thursday 20 September 2001 08:58 am, mlw wrote:
> Now that GreatBridge is gone. (I'm pretty sad about that, they looked like
> they were working on some cool stuff.)
> Has this changed, in any way, the development path of PostgreSQL?
Just my personal opinion:
While PostgreSQL was developed p
"Marc G. Fournier" wrote:
> Okay, its updated effective a few minutes ago ... and the upate should
> work as well ...
Should ...
~/pgsql-cvs/pgsql/src/interfaces/ecpg/preproc > cvs status preproc.y
cvs server: failed to create lock directory for
`/projects/cvsroot/pgsql/src/interfaces/ecpg/prep
Hi,
This isn't working for me either (no existing checkout) :
[justin@justinspc cvs]$ cvs -d
:pserver:[EMAIL PROTECTED]:/projects/cvsroot login
(Logging in to [EMAIL PROTECTED])
CVS password: <>
[justin@justinspc cvs]$ cvs -d
:pserver:[EMAIL PROTECTED]:/projects/cvsroot co pgsql
cvs server: Upda
Now that GreatBridge is gone. (I'm pretty sad about that, they looked like they
were working on some cool stuff.)
Has this changed, in any way, the development path of PostgreSQL?
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, p
Okay, its updated effective a few minutes ago ... and the upate should
work as well ...
On Thu, 20 Sep 2001, Christof Petig wrote:
> "Marc G. Fournier" wrote:
>
> > should be four hours, but I haven't had a chance, with the newest
> > worm/virus going around right now having killed our core rou
http://anything.ca.org goes to the same IP address. It has nothing to do
with postgres
- Original Message -
From: "Serguei Mokhov" <[EMAIL PROTECTED]>
To: "PostgreSQL Hackers" <[EMAIL PROTECTED]>
Sent: Wednesday, September 19, 2001 8:57 AM
Subject: [HACKERS] [OT] http://www.postgresql.ca
On Wed, 19 Sep 2001, Serguei Mokhov wrote:
> Just discovered, by mistyping the www address...
>
> Interesting, whom does this one belong to?
> http://www.postgresql.ca.org
Probably http://www.ca.org/ Cocaine Anonymous
CAWSO, INC (CA5-DOM)
3740 OVERLAND AVE SUITE C
LOS ANGELES, CA 90034
Christopher Kings-Lynne wrote:
> > While you're at it, could you please fix this error:
> >
> > ~/pgsql-cvs/pgsql > cvs -z3 update -dP
> > cannot create_adm_p /tmp/cvs-serv2966/ChangeLogs
> > Permission denied
>
> Instead of checking out over your existing checkout, checkout to a new dir
> and th
Just discovered, by mistyping the www address...
Interesting, whom does this one belong to?
http://www.postgresql.ca.org
--
Serguei A. Mokhov
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(se
> While you're at it, could you please fix this error:
>
> ~/pgsql-cvs/pgsql > cvs -z3 update -dP
> cannot create_adm_p /tmp/cvs-serv2966/ChangeLogs
> Permission denied
Instead of checking out over your existing checkout, checkout to a new dir
and there's no problem.
Chris
31 matches
Mail list logo
