Hello All!
Somebody told me that DB2 has replication.
Does PostgreSQL has it also?
Anyway, does anybody here know the difference between
PostgreSQL and DB2?
Thanks.
Sherwin
---(end of broadcast)---
TIP 2: you can get off all lists at once with
If I have a process which is inserting/updating tuples and run a vacuum
while that process is going, will the vacuum wait for the process to
finish? Or, will I have a problem with the db? How about the other way:
doing a insert/update while a vacuum is running?
Thanks.
-Tony
--
hicham bouzdad wrote:
>Hello everyone,
>
>in Postgresql RDBMS ,
>how can i get informations aboutacces permissions on existing obje
>cts
>?
>
>I alredy know that ( psql \z )do this ;
>but 'w' meansupdate OR delete ! (it's not the sa
What do you mean
'w' meansupdate OR delete ! (it's not the same thing)
?
Do you want to know if somebody only could access (select)?
If he has "r", he has select access on that object.
Access information certaintly includes all (select, alter, update, insert, delete).
---
Banghe
Hi!
Is there a way of setting autocommit off in psql?
Being used to oracle's SQL*Plus, I fell kind of nervous every time i find
out that I forgot to start a transaction by myself.
Running PostgreSQL 7.0.2 on i686-pc-linux-gnu, compiled by gcc 2.95.3 on
Mandrake 7.2 preinstalled. when booting,
Hello everyone,
in Postgresql RDBMS ,
how can i get informations aboutacces permissions on existing objects
?
I alredy know that ( psql \z )do this ;
but 'w' meansupdate OR delete ! (it's not the same thing)
can someone , please, tell me if it is p
Peter Eisentraut wrote:
> William L James writes:
> > script - su -l postgresql -c "/usr/bin/pg_ctl -D $PGDATA -p
> > /usr/bin/postmaster start >>/var/log/postgresql 2>&1"), but
> > when the weekly logrotate.d function kicks in, Postgres logging
> > stops.
> The logging probably continues to go
William L James writes:
> script - su -l postgresql -c "/usr/bin/pg_ctl -D $PGDATA -p
> /usr/bin/postmaster start >>/var/log/postgresql 2>&1"), but
> when the weekly logrotate.d function kicks in, Postgres logging
> stops.
The logging probably continues to go to the rotated-away file. The
typic
Hi there:
We are running PostgreSQL 7.0.2 on RedHat Linux 6.2 and
have encountered a few strange problems that continue to
elude us - namely INSERT and DELETE functions that end
abnormally, but do not include any information as to why (the
JDBC connection just seems to have gone away). Trying to
