Oliver Elphick wrote:
You can't.
Quote from the manual:
So long as no deadlock situation is detected, a transaction
seeking either a table-level or row-level lock will wait
indefinitely for conflicting locks to be released. This means it
is a bad idea for applicatio
On Tue, 2003-10-14 at 21:17, Sam Carleton wrote:
> But how do I see what users exist for the database? Because I was
> the user postgres when I created the database, does that mean there
> was a postgres user added during creation? If not, what user am I
> when I run psql as postgres? If I am po
j sk <[EMAIL PROTECTED]> writes:
> While trying to delete ~8000 rows from a table which
> has about 10 foreign keys and are triggered to cascade
> on delete, I get this error:
> ERROR: Memory exhausted AllocSetAlloc(1124)
Could we see a complete reproducible example? I'm not aware of any
memory l
On Tue, Oct 14, 2003 at 21:17:16 -0400,
Sam Carleton <[EMAIL PROTECTED]> wrote:
>
> But how do I see what users exist for the database? Because I was
One way is to use the \du command in psql.
> the user postgres when I created the database, does that mean there
> was a postgres user added dur
Ok, I am a newbie, but I simply cannot find anything in the
documentation so I hope you all are kind to me...
I have installed Postgres 7.3.4 (will reinstall once I get OpenSLL
compiled into it). I created the postgres user, and the first
database. As the postgress user, I am able to run psql an
Hi all,
While trying to delete ~8000 rows from a table which
has about 10 foreign keys and are triggered to cascade
on delete, I get this error:
ERROR: Memory exhausted AllocSetAlloc(1124)
Im running PG7.3.4 with 256MB memory.
I looked up this info but 'ulimit' and 'limit' arent
available:
http
I am having problems compiling Postgres 7.3.4 on a UltraSPARC 10
running Solaris 8. It compiled fine when I only compiled with perl
and python, but when I try to recompile with ssl, I get errors:
make[2]: Entering directory `~/src/postgresql-7.3.4/src/interfaces'
make[3]: Entering directory `~/sr
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED] (Oliver
Elphick) transmitted:
> On Mon, 2003-10-13 at 11:30, Szabó Péter wrote:
>> Hi!
>>
>> I have a lock problem. If i lock a record with SELECT FOR UPDATE, than
>> i try to lock again, the process just wait until the reco
Gary Stainburn <[EMAIL PROTECTED]> writes:
> Am I right in thinking that dropdb actually connects using the template1
> database to enable it to work, and that the connection is not closing quick
> enough when dropdb finishes, thus causing the problem?
Yes. I'd suggest issuing the DROP and CREA
On Tue, Oct 14, 2003 at 11:32:03AM +0200, Daniel Rubio wrote:
> How I could solve this?
Upgrade to 7.3 and use the schema support to do it for you.
A
--
Andrew Sullivan 204-4141 Yonge Street
Afilias CanadaToronto, Ontario Canada
<[EMAIL PROTE
On Mon, 2003-10-13 at 11:30, Szabó Péter wrote:
> Hi!
>
> I have a lock problem. If i lock a record with SELECT FOR UPDATE, than
> i try to lock again, the process just wait until the record free. But
> i have to send a message to the user like 'The record is locked, try
> later.'. But i can't. H
On Tuesday 14 Oct 2003 4:32 pm, Gary Stainburn wrote:
> Hi folks,
>
> I've got two totally seperate databases that I'm working on at the moment,
> the only thing they have in common is the server that they're on
> (RH7.3+Errata)
>
> For each of these databases I have a file containing the SQL comma
Hi!
I have a lock problem. If i lock a record with
SELECT FOR UPDATE, than i try to lock again, the process just wait until the
record free. But i have to send a message to the user like 'The record is
locked, try later.'. But i can't. How can i do this?
Matyee
Hi folks,
I've got two totally seperate databases that I'm working on at the moment, the
only thing they have in common is the server that they're on (RH7.3+Errata)
For each of these databases I have a file containing the SQL commands to
create and populate the various tables, and bash script w
"Pichelman, Scott" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] /root]$ pg_dump -h 127.0.0.1 -p 5432 template1 -f
> holt_admin_db.dump
> getAggregates(): SELECT failed. Explanation from backend: 'ERROR:
> Attribute 'aggtransfn1' not found
You seem to be using a really ancient version of pg_du
Hi there,
We have just implemented a similar system on a RedHat AS2.1 cluster, Two
Dell PowerEdge 2650s (1x2.8GHz Xeon, 2x2Gb RAM) connected to a Dell
PowerVault220S disc array via Perc 3/DC cards. Runs like a dream.
We have two logical hosts, one for the live environment, the other for the
test.
Hiya,
We're looking into ways to cluster our database servers and
shared storage. Here's the low-down on our servers... all
run RedHat 7.3 with a few patches and are dual PIII 1.4GHz,
2GB, mirrored internal 36, Qlogic 2310 HBA to a LUN on our
Hitachi. PostgreSQL 7.3.3 is installed from source an
Daniel Rubio <[EMAIL PROTECTED]> writes:
> I'm mantaining a Postgres installation on an ISP, and I see a relativly
> important security issue.
> I can connect to postgres with a normal user login and take a look to
> the database structure of all the other databases on the installation.
That is
On Tue, 14 Oct 2003, Daniel Rubio wrote:
> And I still can to look at the others database structure (connecting as
> a non privileged user) ...
>
Did you try setting search_path in postgresql.conf to just '$user'?
You'll also need a schema for each user.
perhaps db_user_namespace does this? I di
Hi to all
I'm mantaining a Postgres installation on an ISP, and I see a relativly
important security issue.
I can connect to postgres with a normal user login and take a look to
the database structure of all the other databases on the installation.
This is very visual with PGadmin. I connect a
20 matches
Mail list logo
