Stephan Richter wrote:
>
> >I can see in ftp.postgresql.org/pub, the file postgresql-7.0RC1.tar.gz.
> >
> >What ORC1 stands for? Is it the non-beta version?
>
> Version 7.0 Release Candidate 1. Yes, this means if no bugs are found, it
> will be 7.0. I saw this version already early last week, e
At 10:17 PM 24-04-2000 -0400, Mike Mascari wrote:
>Lincoln Yeoh wrote:
>PostgreSQL implements SELECT...FOR UPDATE to allow for the
>sequence you'be described:
>
>Session 1:
>
>BEGIN;
>SELECT webuser FROM webusers WHERE webuser = 'webuser1';
>
>Session 2:
>
>BEGIN;
>UPDATE webusers SET webuser = 'w
Have you tried running AB against some of the pages and watching the
connections happen? Also, try playing around with the cache. I found
that I could change the load times and db performance by playing with
Zope db caching. I would also hate to mention it but 7 is still
beta. Can you try it
Stephan Richter wrote:
>
> Hello everyone,
>
> This is a help message to every mailing list, I think this issue could be
> related to. We are in production and 5000 flyers (45000 follow) were sent
> out and the site keeps giving problems.
>
> I use:
> Zope 2.1.4, PyGres 2.x, Apache, and PostGre
On Mon, 24 Apr 2000, Stephan Richter wrote:
>
> >I can see in ftp.postgresql.org/pub, the file postgresql-7.0RC1.tar.gz.
> >
> >What ORC1 stands for? Is it the non-beta version?
>
> Version 7.0 Release Candidate 1. Yes, this means if no bugs are found, it
> will be 7.0. I saw this version alr
>Do you know if Edmund (Mergl) has written a DBD driver for Pg7 yet?
I do not know, since I don't know what a DBD driver is. I am really not a
DB expert. I am using databases for serving a lot of data to Web pages. :)
Reagrds,
Stephan
--
Stephan Richter - (901) 573-3308 - [EMAIL PROTECTED]
CBU
At 06:21 AM 4/25/00 -0400, J. Atwood wrote:
>Have you tried running AB against some of the pages and watching the
>connections happen? Also, try playing around with the cache. I found that
>I could change the load times and db performance by playing with Zope db
>caching. I would also hate to
Hi all,
Trying to make a driver for WinDesign (Merise modelisation) to Postgresql with
the help of CECIMA company.
Q:
==
Is max length of Table, DB, Attribut Name will change in V7 ?
Having this in V6.5 :
=
Max table name : 31 caracteres
Max attribut name : 31 caracteres
Max D
Stephan Richter wrote:
>
> >Do you know if Edmund (Mergl) has written a DBD driver for Pg7 yet?
I am running DBD::Pg 0.93 with pg7 and it works fine.
And so am I.
Andy
On Tue, 25 Apr 2000, Ed Loehr wrote:
> Stephan Richter wrote:
> >
> > >Do you know if Edmund (Mergl) has written a DBD driver for Pg7 yet?
>
> I am running DBD::Pg 0.93 with pg7 and it works fine.
>
On Tue, Apr 25, 2000 at 08:02:41AM -0500, Stephan Richter wrote:
>
> >Do you know if Edmund (Mergl) has written a DBD driver for Pg7 yet?
>
> I do not know, since I don't know what a DBD driver is. I am really not a
> DB expert. I am using databases for serving a lot of data to Web pages. :)
I
Manuel Lemos wrote:
>
> >> >Plus if you get a warning/error, Postgresql _requires_ you to rollback,
> >> >whereas many other databases don't.
> >>
> >> That's what Metabase expects. When there is an error, you should rollback
> >> before exiting a transaction with AutoCommit(Off).
> >>
> >> I not
Peter and Harold (and all):
I just tried this with current CVS sources. While it _does_ allow one to
continue after SQL syntax errors, and 'relation not found' type errors,
it makes a mess if the error is caused by a constraint firing, such
as a unique column constraint. I ended up with the dead t
On Mon, Apr 24, 2000 at 09:23:48PM -0700, Joachim Achtzehnter wrote:
>
> This is good to hear. I suspect, though, that to support statement-level
> aborts more is needed than an overhaul of the error system. Statement
> level aborts are essentially a form of nested transaction, i.e. the
> ability
I have not researched this issue thoroughly, or even superficially, but
I understand that PostgreSQL has something called multi-version
concurrency control (MVCC). This is, I'm told, a GOOD THING, and I
believe it. But the documentation and tutorials on MVCC are far too
terse for me to feel comfor
Hi,
I'm having this message when trying to perform
a query.. someone knows what do I have to do to
fix it?
Thanks
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
We have lost
Teruel Tony wrote:
>
> Hi,
>
> I'm having this message when trying to perform
> a query.. someone knows what do I have to do to
> fix it?
>
> Thanks
>
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally
> before or
Teruel Tony wrote:
>
> I'm having this message when trying to perform
> a query.. someone knows what do I have to do to
> fix it?
>
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally
> before or while processing the
Hi,
The query is simple:
select count(*) from table;
I have the same error message with almost all queries,
I'm trying to debug what's new on that table (data)
because it was working fine..
The version I'm using:
PostgreSQL 6.5.3 on i586-pc-linux-gnu, compiled by gcc egcs-2.91.66
The tabl
Thanks Stephan, dropdb worked just fine. Also, I was not at all offended by
your previous suggestion. I'm still pretty new to Linux.
This issue surfaces an opportunity for me to help the cause. As I go
through the process of setting up PostgreSQL 7.0 and developing a new
database in it, I coul
> Hello -
>After reading the documentation several times, and looking at
> the archives, I'm very confused. The PL/pgSQL documentation states
> that :
Looks like you're confused.
>
> [<>]
> FOR record | row IN select_clause LOOP
>statements
> END LOOP;
>
> is valid, and after having
I'm trying to get IMP to work, and I need to create 2 databases which I have
problems creating.
What I get is this:
GRANT SELECT, INSERT, UPDATE ON active_sessions, auth_user, auth_user_md5 TO nobody;
ERROR: aclparse: non-existent user "nobody"
I don't know how to add the user nobody to grant
On Mon, 24 Apr 2000, Andrew Snow wrote:
> > When we are sure all platforms support 64-bit int's, we will move in
> > that direction.
>
> Sorry if this is a stupid question, but couldn't you fairly easily make it
> an option at compile time? To use either 32 or 64 bit OID's.
> (And, less importan
For me it seems more a design problem than the length of internal number
Why not create a table with 2 field containing int, setting the primary key
on both of them and running a sequencing scheme on both as if it was a
single number
There are no more limitations anymore, as if you know
> Is this necessarily a good solution? If you use 64-bit OIDs, some joker
> will just hook up a several-terra-byte disk array to his machine, try to
> store the location of every molecule in the universe and break it.
If you have to have OIDs at all, its a lot better than a 32 bit number. I
th
>
>
> > Is this necessarily a good solution? If you use 64-bit OIDs, some joker
> > will just hook up a several-terra-byte disk array to his machine, try to
> > store the location of every molecule in the universe and break it.
>
> If you have to have OIDs at all, its a lot better than a 32 bit
At 10:58 AM 24-04-2000 -0500, Ed Loehr wrote:
>Good point. And you can combine the check David suggests with the insert
>statement, e.g.,
>
> INSERT INTO mytable (id, ...)
> SELECT 7, ...
> FROM mytable
> WHERE NOT EXISTS (SELECT * FROM mytable WHER
Teruel Tony wrote:
>
> Hi,
>
> The query is simple:
>
> select count(*) from table;
>
> I have the same error message with almost all queries,
> I'm trying to debug what's new on that table (data)
> because it was working fine..
>
> The version I'm using:
>
> PostgreSQL 6.5.3 on i586-pc-lin
Today, in a message to pgsql-general, Ross J. Reedstrom wrote:
>
> On Mon, Apr 24, 2000 at 09:23:48PM -0700, Joachim Achtzehnter wrote:
> >
> > I suspect, though, that to support statement-level aborts
> > more is needed than an overhaul of the error system. Statement
> > level aborts are essenti
In a message to Ed Loehr and pgsql-general, Lincoln Yeoh wrote:
>
> Transaction A
> begin;
> insert into test (a,b) select 4,'four' from test
> where not exists (select * from test where a=4);
>
> Transaction B
> begin;
> insert into test (a,b) select 4,'four' from test
> where not exists (select
Hey all,
Readline functionality not working in psql.
I've installed PostgreSQL 7.0 RC1 on RedHat 6.2. I have configured using:
--with-libraries=/usr/lib
which is where the libreadline.so.3 file is. One of the things I've
noticed, although I'm not sure of it's significance, is that when th
Using 6.5.3 on SuSE 6.4 and program kpgsql.
Dumped data to a ';' delimited file wherein the date looks like
'1997-12-27'. The date field may be null.
Created the appropriate table using variously date/datetime/timestamp for
data type, set datestyle to ISO/SQL/others.
The copy command is
Using 6.5.3 on SuSE 6.4
Create a new table works and the results box shows 'CREATE'.
The next query, however, reports that a query is still in progress. Tried
the new query button and simply erasing last query entered.
Seems the only way to correct this is to disconnect.
Upon reconnect I can s
33 matches
Mail list logo
