On Tue, Sep 12, 2006 at 06:11:19PM +0600, Thilina Ranaweera wrote:
> I am new to PostgreSql .Please tell me how to define user access only to
> selected tables
See the GRANT and REVOKE commands.
http://www.postgresql.org/docs/8.1/interactive/ddl-priv.html
http://www.postgresql.org/docs/8.1/int
On Tue, Sep 12, 2006 at 02:26:11PM +0800, Liustech wrote:
> My postgres can not start up, I get this error message:
>
> postmaster successfully started
> /usr/bin/postmaster: real and effective user ids must match
How are you starting the postmaster? The error suggests that the
postmaster or th
Tom Lane wrote:
"Paul B. Anderson" <[EMAIL PROTECTED]> writes:
I did delete exactly one of each of these using ctid and the query then
shows no duplicates. But, the problem comes right back in the next
database-wide vacuum.
That's pretty odd --- I'm inclined to suspect index corruption.
I
Hello Sir,
I am using
PostGreSql ,I want an oledb provider for the postgre in order to connect
through.net to a postgre Database, I installed the pgoledb.dll and I registered
it and in the connection string I am using the “Provider=PostgreSQL.1 . .
. ,but the following error is occurrin
I am new to PostgreSql .Please tell me how to define user access only to selected tablesThanks
My postgres can not start up, I get this error
message:
postmaster successfully started/usr/bin/postmaster: real
and effective user ids must match
and
Sep 12 14:18:26 TWeb su(pam_unix)[6683]: session opened for
user postgres by (uid=0)Sep 12 14:18:26 TWeb su(pam_unix)[6683]: session
c
The postgres commands work fine to postgres user but it doesn’t
work to a random user account
I already created the user on postgres
desktop:~# su - postgres
[EMAIL PROTECTED]:~$ createuser -a -d oacsbr
and set on .bashrc
LD_LIBRARY_PATH=:/usr/local/pgsql/lib:/usr/local/pgsql/li
I forgot to contextualize,
env | grep PATH :
[EMAIL PROTECTED]:~$ env | grep
PATH
PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
Funny thing, speaking about
full paths... there is no psql command in "/usr/bin/"
[EMAIL PROTECTED]:~$ ls -l
/usr/bin/psql
ls: /us
You said "local Reiser FS." Maybe repeat on one of the others, Ext3/JFS?
Tom asked about hardware issues, is there nothing in syslog
that relates to the timing of the event? I don't recall you
responding in public to this. Maybe I missed it.
Just musing...
On Wed, Sep 13, 2006 at 12:5
Someone else was doing the vacuum that didn't complete this last time
and they started it at night so no other queries were running. I wasn't
monitoring I/O usage at the time and in the past I just always removed
the indexes and vacuumed when this happened.
This is on a Solaris server, would y
Ellen Cyran <[EMAIL PROTECTED]> writes:
>> Hm, that should be OK. What do you have maintenance_work_mem set to?
> It's set at the default 16384.
That should be plenty for getting rid of a million or so tuples. I'm
wondering if you are seeing some weird locking effect. Is the VACUUM
constantly
It's set at the default 16384.
Tom Lane wrote:
Ellen Cyran <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
By "vacuum" do you mean VACUUM FULL?
No, I mean vacuum analyze.
Hm, that should be OK. What do you have maintenance_work_mem set to?
regards, tom lane
Ellen Cyran <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> By "vacuum" do you mean VACUUM FULL?
> No, I mean vacuum analyze.
Hm, that should be OK. What do you have maintenance_work_mem set to?
regards, tom lane
---(end of broadcast)---
"Mr. Dan" <[EMAIL PROTECTED]> writes:
>> How are you doing the copies, exactly? SQL COPY command, psql \copy,
>> something else?
> We've tried SQL COY and psql \copy and always get random results - 0,1, or 2
> blocks of 25 rows missing.
Hmph. If it happens with a SQL COPY command then psql see
No, I mean vacuum analyze. I'll vacuum verbose and see about adjusting
the fsm. Thanks.
Tom Lane wrote:
Ellen Cyran <[EMAIL PROTECTED]> writes:
We have a database that periodically we perform large updates, around
a million records, after that the vacuum will run for 12 hours without
compl
Ellen Cyran <[EMAIL PROTECTED]> writes:
> We have a database that periodically we perform large updates, around
> a million records, after that the vacuum will run for 12 hours without
> completing. After that, I typically remove the 2 indexes and 1
> constraint on the largest table, 7 million re
We have a database that periodically we perform large updates, around
a million records, after that the vacuum will run for 12 hours without
completing. After that, I typically remove the 2 indexes and 1
constraint on the largest table, 7 million records, and the vacuum will
complete in a coupl
This is pretty confusing. You mean that groups of 25 adjacent rows were
missing in the output?
Yes, isn't that interesting? It's always in a group of 25 rows. This is
always random. Say 800,000 to 800,025 out of 12 million represents one
random group of 25 rows.
What's the (24+1) supp
Hello,
I am running into a problem on a RHEL3 systems, running PostgreSQL 7.4
We have a database, which consistently consumes more and more of the
disk space in it's lvol until it reaches 100%. So far, we have tried
to run a full vacuum on the database, with limited success.
Eventually, we
19 matches
Mail list logo
