at whatever reader they use, everyone can cope with messages that
are as short as reasonably possible and contain just relevant text,
whether new or quoted - and there seems to be a consensus that this is
what is important, not whether your comments are at the top or bottom.
Thanks,
Robin
anner will immediately
use the index after you've created it - you might have to run analyze on
the ap_attribute table first.
Hope this helps,
Robin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
helps,
Robin
On Tue, 10 Apr 2012 11:44:08 +0530, raghu ram wrote:
On Tue, Apr 10, 2012 at 11:21 AM, Kiruba suthan wrote:
Could you help me how to clean up DB Cluster folder and reclaim disk
space please? And please give me some insight into how data is
organized in DB Cluster and what should I
t tuples_only
dbname=>\o |/bin/bash
dbname=>select 'id';
uid=0(root) gid=0(root)
groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)
There are many more sophisticated examples. The only solution is not to
grant sudo to anyone you wouldn't grant root to.
Cheers,
reate an audit trail by adding in username capture in
the software is doomed to being circumvented by anybody with root access
who doesn't want to be traced.
For example:
robin$ su - root
root# su - kgama
kgama$ su - root ... do something bad.
Now it looks like you did it, even though it was
What do you want to have happen to the timestamp/user?
You can obviously do:
update test set t4 = 9, user = , timestamp =
where t1 = 001;
I'm assuming you're trying to store the user and timestamp somewhere
else, though?
Robin
On Wed, 2012-03-14 at 12:44 +0200, Khangelani
On Mon, Dec 5, 2011 at 9:53 PM, Tom Lane wrote:
>
> There are interlocks against that ... although if you were foolish
> enough to manually remove postmaster.pid, you could defeat them :-(
>
We didn't remove postmaster.pid
--
Yann
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.o
>
> First things first: Before you do anything else, shut down
> PostgreSQL and make a copy of the data directory tree.
>
> http://wiki.postgresql.org/wiki/Corruption
>
Did it.
> Second, please post information about your environment. What
> version of PostgreSQL is this? What is your OS? What
Hi,
Earlier this afternoon, our database crash with a stacktrace.
We killed hardly the remaining postgres process left.
Since then it's been hell !!!
First Postgres told us that there was a corrupted index and we needed
to reindex it.
We couldn't do it because there was duplicate id in the table.
gt;
> Please let me know how I could start working on my thesis.
>
One would hope _you_ would know that ... else why are you doing it.
All the documentation will be on the main postgres site, as is the source
code:
http://lmgtfy.com/?q=postgres+documentation
http://lmgtfy.com/?q=p
onstrained)
you might want to revert that parameter.
Cheers,
Robin
On Fri, 16 Apr 2010 15:56:03 -0400, Alexandre Leclerc
wrote:
> Le 2010-04-16 15:44, Tom Lane a écrit :
>> "Kevin Grittner" writes:
>>
>>> "Joshua D. Drake" wrote:
>>>
e sure which order the queries were inserted, although if you're using
statement level logging, you'll should see distinct query and backend start
timestamps anyway.
Just an idea - never tried it myself - so probably best to test it out on
a test database of some sort first!
Cheers,
Ro
don't think that the psql \c command allows you to bypass pg_hba
configuration, so I wonder if your pg_hba.conf file is broken - have you
tried psql ? I am pretty sure that there is little or no
difference between:
psql
and
\c
Cheers,
Robin
KyLiE wrote:
Hi all, I'm quiet n
ocs.
Hope this helps,
Robin
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
s are frozen for the cluster (except that you can change the
encoding for a specific database within the cluster, but that isn't
going to do what you want, which is change the sort order).
So, if you can re-run initdb then you can do what you want without
recompiling.
See "man initdb
in the same way).
Unless you really need the NFS mount I might be inclined to turn it off
for a while and see what happens ...
Cheers,
Robin
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
isks). I don't think it
matters how long it takes to make the base backup, provided you are
always copying the WAL files too.
Hope this helps,
Robin
Steve Burrows wrote:
I am struggling to find an acceptable way of backing up a PostgreSQL
7.4 database.
The database is quite large, current
Can I delete these files ? Or give me an advice, please.
When I had a similar problem it turned out that I had exceeded the
limits of my FSM and thus the stats table in particular was growing as
it was unable to reuse rows.
Check your FSM size in postgresql.conf and see what:
max_fsm_p
d will post the results here if anyone is interested.
Best wishes,
Robin
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
anism to keep the logs
since the last backup you should be able to restore from that last
backup and logs without the data drive. The reverse isn't true - if you
lose the WAL but have the data drive, it may not be consistent ...
Robin
---(end of
HT system (2.6 kernel again, PG 8.0) we found that we had some very
odd performance problems that were hard to reproduce in the lab but
occurred in the live environment a lot. Turning off HT made them go away.
Hope this helps,
Robin
---(end of
(\'192.100.9.51\',\'FirstFloor\')'
However, if I were you I would consider running via a file anyway - if
you save your query into a file then you can use
psql -d temp -f foo.sql
instead. Within the file you can type your query exactly like it should
be with no special esca
to false.
Robin
---(end of broadcast)---
TIP 6: explain analyze is your friend
urn 0 if
the server is running and 1 if the server is no running.
So you could try something like
while ssh $REMOTE pg_ctl -D $CLUSTER status
do
echo "Remote server still running - continuing to wait ..."
sleep 10
done
Hope this helps,
Robin
---(end of broadcast)---
TIP 6: explain analyze is your friend
Andy Shellam wrote:
Robin,
On my part it's simply the fact that I currently have two servers in
different geographical locations - and cost of new hardware is a huge issue.
I have, however, recently developed an interest in rsync but I'm unsure as
to how PG on the standby server wo
e database rather than PITR between the database servers.
I see a lot of interest on this list for the WAL copying solution, and I
am wondering if that is because people have discounted a DRBD solution
or that it has been overlooked?
Thanks,
Robin
---(end of
something like
jdbc:postgresql://192.168.2.1/my_database
Can you post your pg_hba.conf file?
Cheers,
Robin
Leena Puijola wrote:
Hi,
Please can you assist.
I am trying to connect to PostgreSQL via JDBC.
Database version is 8.0.1 and java software version 1.4.2.
I have configured the pg_h
were running on localhost, probably!).
Cheers,
Robin
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
an IP address ...
Robin
sandhya wrote:
Thanks Robin.
What u said is right!
But my problem is i am not trying connecting from any remote client.
In my ConnectionInfo if i mention the host as,
host=localhost.The connection is successful.
But the same if i give my localsystem IP where my server is ru
we
use the -i on the command line to the postmaster process.
Hope this helps,
Robin
sandhya wrote:
hi,
I am using postgres8.0.3 on windows.When i am compiling a small sample i am facing problem in connection information.
I have given entry in my pg_hba.conf file:
hostall
Then:
n_tup_upd+X < 1000 + (2.0 * (reltuples+X))
I see that in 8.1.x this has been resolved by defaulting the scale to
0.4. Rightly or wrongly I have set my scale to 0.3.
Thanks for all the help you've offered so far.
Robin
---(end of broadcast)-
size: 1000 relations + 2 pages = 182 kB
shared memory.
INFO: free space map: 6 relations, 19975 pages stored; 29600 total
pages needed
DETAIL: Allocated FSM size: 1000 relations + 20000 pages = 182 kB
shared memory.
I don't actually understand exactly what this is telling me though
.
At least not before the number of tuples has climbed to beyond that
count based on my experience to date!
Robin
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your
of scale for a while and see
if it makes things any better.
Thanks for all the help,
Robin
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
t see:
DEBUG: 1 All DBs checked in: 478378 usec, will sleep for 300 secs.
DEBUG: 2 All DBs checked in: 73336 usec, will sleep for 300 secs.
Implying that there isn't anything doing right now (the staff are all
gone, so there is no activity on the database as I type, and we know it
won
50% slack - I just don't
understand why pg_statistic grows without bound and I am concerned that
the size of the stats table might be causing me some performance issues
(this is fear rather than fact).
Thanks again,
Robin
---(end of broadcast)
uum not
consider vacuuming of the stats tables?
Thanks in advance for any help you can offer me ...
Robin
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Title: -- CONFIDENTIALITY NOTICE --
-- CONFIDENTIALITY NOTICE --
This
message is intended for the sole use of the individual and entity to whom it is
addressed, and may contain information that is privileged, confidential and
exempt from disclosure under applicable law. If you are not the
38 matches
Mail list logo
