On Tue, Jul 08, 2036 at 07:36:11AM +, LeSI wrote:
> Jun 1 00:59:06 upa kernel: postmaster(11156): unaligned trap at
> 00012013e320: 00011fff9d05 28 1
>
> appears in the messages (syslog)
> running pgsql 6.5.3 in an alpha UP2000 , with redhat 6.1
> rpm installation.
>
> how can i fix
ive been compiling pgsql 7 in an alpha server (UP2000 / 2 cpus)
steps that i did:
1- configure
2- make
3- make install
4- adduser postgres
5- mkdir /var/lib/pgsql
6- chown postgres.postgres /var/lib/pgsql
7- su postgres ; cd /var/lib/pgsql
8- initdb -D /var/lib/pgsql
but , it stops there and fe
Jun 1 00:59:06 upa kernel: postmaster(11156): unaligned trap at
00012013e320: 00011fff9d05 28 1
appears in the messages (syslog)
running pgsql 6.5.3 in an alpha UP2000 , with redhat 6.1
rpm installation.
how can i fix it?
--
[LeSI][[EMAIL PROTECTED]]
[RH LiNUX][ICQ UIN 1207634]
[Buen
I've take a look at the FAQ on www.postgresql.org
A few questions and a little problem about FAQ html that I noticed.
> I have added this to the PostgreSQL FAQ. Thanks.
>
>
> > I am running postgresql 6.5.2 on FreeBSD. I am developing a data warehouse
> > here at Utah State University. A qu
I have a Postgres application that must run 24x7. If postgres needs to be
vacuumed periodically, must I take the application offline, or is it enough
to disallow write (INSERT/UPDATE) access while allowing read access?
I hope it is the latter, as I have a large data set and there are
transaction
I have added this to the PostgreSQL FAQ. Thanks.
> I am running postgresql 6.5.2 on FreeBSD. I am developing a data warehouse
> here at Utah State University. A quick look at the docs leaves the following
> questions:
>
> 1. what is the maximum size for a database?
> 2. what is the maximum s
> > 2.Why the authentication system is not integrated in
> > the system databases of pgSQL,like in MySQL for
> > example?
>
> Because there's a bootstrapping problem: You would have to connect to the
> database to change the authentication settings, but in order to connect
> you have to be authe
Wallingford, Ted writes:
> I am using 6.3 in this case.
I'm sorry but that is pre-historic era around here and no one really
remembers what the problems might have been back then (other than that
they were surely plenty). Upgrading might be your best bet on all fronts.
--
Peter Eisentraut
R D writes:
> 1.I think it will be good pgSQL to accept the
> "GRANT ALL ON * TO SOMEUSER;" and
> "REVOKE ALL ON * FROM SOMEUSER;" so are there
> any plans in implementing this? Does anybody knows?
I think so too. We'll take it under advisement.
> 2.Why the authentication system is not integ
Norbert Meissner wrote:
>
> > > How do you go beyond 2gigs on a single file on ext2fs (like
> > > the major linux distributions delivering) ? magic?
> >
> > Split the files into 1 gig segments.
> >
>
> Excuse my dumb questions, but is this a capability of linux or postgresql ?
> Can you point me
> > > How do you go beyond 2gigs on a single file on ext2fs (like
> > > the major linux distributions delivering) ? magic?
> >
> > Split the files into 1 gig segments.
> >
>
> Excuse my dumb questions, but is this a capability of linux or postgresql ?
> Can you point me to a location where i can
> > How do you go beyond 2gigs on a single file on ext2fs (like
> > the major linux distributions delivering) ? magic?
>
> Split the files into 1 gig segments.
>
Excuse my dumb questions, but is this a capability of linux or postgresql ?
Can you point me to a location where i can read more ?
Tha
> >
> >
> > What PostgreSQL version are you running? We are able to go >2 gigs. I
> > think some have 10 gig tables, even on Linux. What version are you
> > using?
>
> How do you go beyond 2gigs on a single file on ext2fs (like
> the major linux distributions delivering) ? magic?
Split the fi
>
>
> What PostgreSQL version are you running? We are able to go >2 gigs. I
> think some have 10 gig tables, even on Linux. What version are you
> using?
How do you go beyond 2gigs on a single file on ext2fs (like
the major linux distributions delivering) ? magic?
Norbert
Thanks! But this answers gave rise to some new
questions.
1.I think it will be good pgSQL to accept the
"GRANT ALL ON * TO SOMEUSER;" and
"REVOKE ALL ON * FROM SOMEUSER;" so are there
any plans in implementing this? Does anybody knows?
2.Why the authentication system is not integrated in
the sy
> Hi Mari,
>
> as far as i know is the table size limited through the size of
> int4 (=size of oid, 32 Bits). This means that you can have an
> amount 4 "Gigarows" in one table.
>
> There are some people working on the 2 GB Limitation on the
> Linux filesystem. I remember an article about this i
>Excuse me for the latest message , i've found the solution
>
> localallpasswordpasswdfile
>
> Now , passwords are stored (and crypted) in passwdfile .
> The authentication with psql is ok
>
> But pgaccess still use the password in clear in pg_shadow . Is there an
> option ,
Bruce Momjian wrote:
> >Excuse me for the latest message , i've found the solution
> >
> > localallpasswordpasswdfile
> >
> > Now , passwords are stored (and crypted) in passwdfile .
> > The authentication with psql is ok
> >
> > But pgaccess still use the password in clear in
Hi All,
I am trying to enable my web site to create views in a database owned by a
user called ddirpts. Now, the web server runs as nobody, and nobody has a
user and database set up in Postgres.. But the problem is, whenever I have a
cgi program issue a create view query on the ddirpts database,
Hi Mari,
as far as i know is the table size limited through the size of int4 (=size of
oid, 32 Bits). This means that you can have an amount 4 "Gigarows" in one table.
There are some people working on the 2 GB Limitation on the Linux filesystem. I
remember an article about this in a german compu
I read that postgres table size is unlimited.
But, a postgres table is stored into a file, and the size of a file is
limited to approximately 2 Giga Bytes under Linux.
I tried to test this by inserting hundreds of thousands of rows into a table
: my insert queries failed when the file containing
Excuse me for the latest message ,
i've found the solution
local all password
passwdfile
Now , passwords are stored (and crypted) in passwdfile .
The authentication with psql is ok
But pgaccess still use the password in clear in pg_shadow . Is there
an option , i've not set correc
22 matches
Mail list logo