if you doing an update / insert /
delete you may want to wrap it in an explicit transaction and then roll it back.
HTH,
Greg Williamson
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
d
might help with whatever problem you think autovac is causing.
HTH,
Greg Williamson
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Rafael --
<...>
>> Has anyone else seen anything like this ?
>>
>
> Hello
>
> The release notes for 9.2.2 say this:
>
> "... However, you may need to perform REINDEX operations to correct
> problems in concurrently-built indexes, as described in the first
> changelog item below."
>
> Bu
config settings to
see if anything changed (shouldn't have but ...).
Has anyone else seen anything like this ?
I suspect some site error had led to us scoring an own-goal but I thought I'd
ask and see if anyone else has seen this.
Thanks,
Greg Williamson
--
Sent via pgsql-adm
Tom --
>Greg Williamson writes:
>> We want to create a role used by a monitor to check for " in
>> Transaction" with the most restrictive permissions we can on a 8.4.13
>> instance.
>
>> The user has been granted connect privilege to the database
e database and some limited
permissions to user tabhles that need to be monitored. But pg_stat_activity
shows only ""
I've trolled the archives and postgres docs with no success.
Could some kind soul point me in the right direction ?
Thanks!
Greg Williamson
ld not know about.
If it does not run from the command line, that will probably give you a clue.
HTH,
Greg Williamson
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
s of
failures, never repeated. The hand rolled version is a bit safer and a little
less intrusive.
HTH,
Greg Williamson
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Tom --
<...>
>> A cron job dropdb one of the databases and createdb it and then pg_restore.
> Roughly 80GB dump.
>
> So far, my guess is that this is fixed by commits a1f064fc2 + d7598aeea.
>
>> Out production PostgreSQL running a 9.1 variant does not have this problem.
> It does not have
fantastic !
thanks.
greg
>
> From: Jaime Casanova
>To: Greg Williamson
>Cc: "pgsql-admin@postgresql.org"
>Sent: Wednesday, October 17, 2012 10:05 AM
>Subject: Re: [ADMIN] Database size stays constant but disk space keeps
>s
Gabriele --
- Original Message -
> From: Gabriele Bartolini
> To: Greg Williamson
> Cc: pgsql-admin@postgresql.org
> Sent: Wednesday, October 3, 2012 4:41 AM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
> shrinking -- postgres 9.1
>
&
I've done some more testing and the problem seems to be repmgr itself.
A few details below...
- Original Message -
> From: Greg Williamson
> To: Tom Lane
> Cc: "pgsql-admin@postgresql.org"
> Sent: Thursday, September 27, 2012 7:23 PM
> Subject: R
Dinesh --
- Original Message -
> From: Dinesh Bhandary
> To: Greg Williamson
> Cc: "pgsql-admin@postgresql.org"
> Sent: Thursday, September 27, 2012 7:19 PM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
> shrinking -- postgr
Steve --
- Original Message -
> From: Steve Crawford
> To: Greg Williamson
> Cc: "pgsql-admin@postgresql.org"
> Sent: Friday, September 28, 2012 8:59 AM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
> shrinking -- postgres 9.1
Tom --
- Original Message -
> From: Tom Lane
> To: Greg Williamson
> Cc: "pgsql-admin@postgresql.org"
> Sent: Thursday, September 27, 2012 7:55 PM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
> shrinking -- postgres 9.1
Tom --
- Original Message -
> From: Tom Lane
> To: Greg Williamson
> Cc: "pgsql-admin@postgresql.org"
> Sent: Thursday, September 27, 2012 7:14 PM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
> shrinking -- postgres 9.1
Steve (and others who replied):
- Original Message -
> From: Steve Crawford
> To: Greg Williamson
> Cc: "pgsql-admin@postgresql.org"
> Sent: Thursday, September 27, 2012 3:48 PM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
&g
Dear list,
I have a postgres database, 9.1.3, which shows a fairly constant amount of
space used by postgres, but total disk space kees shrinking.
If I restart postgres the space on my file system returns.
This cluster is replicated to another; that custer does not show this problem.
There are
information if you give me some pointers as to what to look
for.
Thanks!
Greg Williamson
postgres(at)db11:5432=# select version();
version
I've got a fairly large table (186 million rows) that is moderately busy ( a
few inserts per second at most) that I am trying to create a trigger on -- it
is just hanging.
Can this be done in 8.3 ? Will it eventually complete ?
Thanks for any advice, information, etc.!
Greg Williamson
Tom, et. al.,
>
> From: Greg Williamson
>To: Tom Lane
>Cc: "pgsql-admin@postgresql.org"
>Sent: Thursday, August 9, 2012 5:35 PM
>Subject: Re: [ADMIN] Question about ALTER TABLE DROP CONSTRAINT on 9.1
Tom --
>
><...>>
>> WTF? That should certainly not happen. Have you perhaps got a script
>> that runs around sending SIGTERM to backends that it thinks are blocking
>> something? Does anything show up in the postmaster log when this
>> happens?
>
>No, we have
64-bit
(1 row)
This table is only updated a few times a minute (mostly inserts and deletes,
some updates), others get hit a lot more (many times a second). pgsql is the
same version and I am on the same server.
Is this known / documented ? Any suggestions (other than not to do this ; -- )
Thanks,
Greg Williamson
A follow up --
<...>
>>> a) quickly relieve the immediate pain
>>
>> Set autovacuum_cost_limit to a smaller value. (Change the
>> postgresql.conf file and do a reload.) I would start by cutting the
>> current value in half.
>> >
>Thanks -- would not have known how to start. But for now, in
Kevin --
<...>
>> a) quickly relieve the immediate pain
>
> Set autovacuum_cost_limit to a smaller value. (Change the
> postgresql.conf file and do a reload.) I would start by cutting the
> current value in half.
>
Thanks -- would not have known how to start. But for now, in
observance of
uture (other than going to manual vacuuming on
a schedule).
Thanks,
Greg Williamson
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
type numeric in the table, and copy the values from the text variant to the
numeric ones with the proper cast one at a time; if it blows up you go back to
resolving issues. Then copy the table using the numeric columns to the desired
destination.
Hopefully others might have better ide
Matheus --
>
>To me seems that it just appended the data to your log. To avoid this set the
>log_truncate_on_rotation to on, but notice that it will replace the old logs.
>
>
Thanks for the suggestion, but we seem to be using this already:
-bash-3.2$ grep log_truncate_on_rotation postgresql.
sf1ddb001 puppet-agent[28309]: Finished catalog run in 10.16
seconds
Feb 7 01:27:43 sf1ddb001 puppet-agent[28309]: Finished catalog run in 10.86
seconds
Feb 7 01:57:59 sf1ddb001 puppet-agent[28309]: Finished catalog run in 10.48
seconds
<...>
Has anyone ever seen anything like this ?
T
0 Feb 6 14:49 1577013889
-rw--- 1 postgres postgres 0 Feb 6 14:49 1577011574
-rw--- 1 postgres postgres 0 Feb 6 14:49 1577011572
-rw--- 1 postgres postgres 0 Feb 6 14:49 1577011568
Are these safe to delete these files ?
Is it safe to delete the directory itself ?
Th
>
Did you actually try this ?
This does not include any references to indexes, constraints or sequences, all
of which it might be useful to recreate.
What I am I missing ? Or is pg_restore just not capable of restoring the full
definition of a table ?
TIA,
Greg WIlliamson
--
S
p without time zone |
Indexes:
"index_hosts_on_name" btree (name)
"index_hosts_on_source_file_id" btree (source_file_id)
Could someone hit with me with a clue stick ? I've tried endless combinations
of ways to restore the whole table with all indexes and hav
e like from all
periods; novels and the like that are no longer under copyright, so lots of
long
classics.
<http://www.archive.org/stream/ataleoftwocities00098gut/old/2city12p_djvu.txt>
for example ... 765K
HTH,
Greg Williamson
--
Sent via pgsql-admin mailing list (pgsql-admin@postgr
hat are the number of rows in those tables ?
It is possible that the planner is doing a sequential scan because the tables
are small and that's faster than doing indexed reads.
Greg Williamson
Don't 'kill -9' the postmaster
Ray,
You don't say what form of quoting you are using, but maybe you could
try doubling up those quotes ?
raise notice ''A is %'',5;
HTH,
Greg Williamson
Senior DBA
GlobeXplorer LLC, a DigitalGlobe company
Confidentiality Not
35 matches
Mail list logo
