, but ...
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
nonsensical combinations. However, a nonsensical combination
could easily cause bad results from upper().
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
?
Did you configure to install into the same directories as before?
(The original pg_config program can remind you of the configuration
and build settings.)
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your
/docs/8.4/static/libpq-threading.html
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
of now() readings. You're out of luck ---
Windows just doesn't expose a call to get the wall clock time to better
than 1 msec.
Keep in mind that whatever the Linux machine is returning might be
largely fantasy in the low-order bits, too.
regards, tom lane
--
Sent via pgsql
.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
postgresql package and not
postgresql-server. It's not psql only but the stuff in that
package is what is expected to be useful on a client-only machine.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription
checkpoint_segments to a
lower number and restarting the database, but to no avail.
Patience. It'll trim down the number of files when it gets around
to it (probably at the next checkpoint, but I don't recall the
exact conditions).
regards, tom lane
--
Sent via pgsql
, how would I duplicate an existing database and call it
with a different name?
Use pg_dump not pg_dumpall.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
file? Those settings obviously didn't take.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
postmaster on the same
port number, which seems like a good thing.)
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Marko Kreen mark...@gmail.com writes:
On 11/12/09, Tom Lane t...@sss.pgh.pa.us wrote:
The other thought is that quickdie should block signals before
starting to do anything.
There would still be possibility of recursive syslog() calls.
Shouldn't we fix that too?
That's what the signal block
that they might be stuck in something
like this. But for now, I'm more interested in a one-line fix that
will deal with the actually observed case ...
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription
wstrzalka wstrza...@gmail.com writes:
I'd like to know how the binary installation I have has been
originally built - in the meaning of ./configure params.
Is there a way to check this?
Run pg_config
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql
it to parse
the config file it's not clear what we could do about that.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
really is marked as not readable by the postgres user, or (probably
more likely on Windows) you have some malfunctioning antivirus
software installed.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription
Kevin Kempter kev...@consistentstate.com writes:
Anyone have any Idea how this could happen?
Corrupt indexes. What PG version are we talking about?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription
other data that
might help somebody reproduce the problem?
BTW, please keep your responses cc'd to the list.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
in the standard
Postgres sources. Presumably it's coming from some EDB-specific code.
I suggest you take it up with EDB's support.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
for now.)
So, when it archives successfully the second time, which if either of
the two mismatched sha1's proves to have been correct?
(I'm still wondering about the possibility that the WAL file is changing
underneath you ...)
regards, tom lane
--
Sent via pgsql-admin
David F. Skoll d...@roaringpenguin.com writes:
Tom Lane wrote:
So, when it archives successfully the second time, which if either of
the two mismatched sha1's proves to have been correct?
The one on the master server (lines wrapped for readability).
However, the sha1 is taken after rsync
Steve Crawford scrawf...@pinpointresearch.com writes:
Tom Lane wrote:
The source and destination servers have to be the same major PG release,
same architecture (no 32-bit vs 64-bit for instance), and built with the
same configure options. OS per se shouldn't matter, but you could
easily get
the
incorrect checksum message?
No; there's no WAL change between 8.3.7 and 8.3.8. What seems more
likely is that you're somehow shipping the WAL files before they're
quite finished.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make
responsibility for vacuuming everything on a reasonable schedule.
That includes the system catalogs. I think you'd be better off taking
the effort to learn to tune autovacuum to fit your requirements.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin
and then reindex to see if the problem goes away.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
David F. Skoll d...@roaringpenguin.com writes:
Tom Lane wrote:
No; there's no WAL change between 8.3.7 and 8.3.8. What seems more
likely is that you're somehow shipping the WAL files before they're
quite finished.
So unless there's a possibility that the master server invokes our archive
.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
or autovacuumed often enough,
it should be no worse than frequent updates in any other table.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
options. OS per se shouldn't matter, but you could
easily get burnt on configure options if you use binaries obtained from
different packagers. Compare pg_config output or check the fields
listed by pg_controldata.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql
Jaime Casanova jcasa...@systemguards.com.ec writes:
On Tue, Oct 20, 2009 at 9:25 AM, Tom Lane t...@sss.pgh.pa.us wrote:
OS per se shouldn't matter
unless you try to do it between windows and some flavor of linux
hmmm ... even there, the only risk factor I see would be incompatible
locale
.
regression=# \d foo
ERROR: column reltriggers does not exist
LINE 1: SELECT relhasindex, relkind, relchecks, reltriggers, relhasr...
^
regression=#
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin
, and that should have gotten logged.
Another possibility is that you've got some non-postgres code loaded
into the backend that is doing exit(1).
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http
it decide to terminate the process.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Anj Adu fotogra...@gmail.com writes:
I have a few databases where the size of pg_attribute 6G..This
keeps growing..
Have you got autovacuum disabled? That should keep the bloat in check
if it's allowed to work normally.
regards, tom lane
--
Sent via pgsql-admin
about enabling autovacuum ...
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
not using
the -d/-D switch as the easiest way to find out which table contains
the corrupt data --- then you'll see the error on a COPY command instead
of a cursor fetch.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes
wraparound, but that isn't going
to cause you any performance problems.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
of stability problems in the
recent past. I'm thinking that there is some underlying problem
with your system -- maybe bad hardware or a nasty kernel bug.
If Postgres were this unstable for everybody, nobody would use it.
regards, tom lane
--
Sent via pgsql-admin mailing
standard_conforming_strings turned on, those backslashes
are going to be eaten by the string-literal parser. So the LIKE code
just sees '_%_username'.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http
a ~/.psqlrc containing commands
that wouldn't work against the older server. Failing that, I'm going
to bet that this is a firewall issue of some sort.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription
the number of check
constraints actually present.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
, but if this is trying to
read the Unix password file directly then it won't work, because
postgres doesn't run as root. You'd need to have an external helper
program of some sort. Afraid I don't use PAM enough to offer specifics.
regards, tom lane
--
Sent via pgsql-admin mailing list
.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
think what you're showing us is a stack trace of an idle postmaster
process, not the process that crashed.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
to belong to that relation, but has attnum
32533. It would be interesting to see the results for
select * from pg_attribute where attrelid = 'largedata'::regclass
What PG version is this exactly, on what platform?
regards, tom lane
--
Sent via pgsql-admin mailing list
informative ...
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
the postmaster by hand
instead of via whatever unhelpful start script you're using.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
major new postmaster
logic to work around.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
|| '.' || relname) DESC
LIMIT 20;
I think maybe you'd better ORDER BY pg_total_relation_size instead.
Also, maybe look further than 20 rows ... maybe the issue is many
thousands of little tables?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin
://www.postgresql.org/docs/8.3/static/storage.html
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
at the output
of the size functions.
select pg_size_pretty(pg_database_size('db1'));
Just to double check here ... you're sure you're naming the correct
database in this call?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes
to
require serious amounts of work, with no guarantee of success. How
desperate are you?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
, and excluded toast
tables, so you are missing those.
2. pg_largeobject ... got any large objects?
3. Bloat in other system catalogs. 5GB of catalog bloat would be
pretty awful, but maybe that's what it is.
Try that last query without the namespace restrictions.
regards, tom
to fix it...
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
of the archives would've led you to
http://archives.postgresql.org/pgsql-novice/2009-08/msg00082.php
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Nigel Metheringham nigel.methering...@dev.intechnology.co.uk writes:
On 17 Sep 2009, at 14:57, Tom Lane wrote:
The symptoms indicate pretty strongly that you forgot about vacuuming
the system catalogs. A plain VACUUM executed in every database, by
a superuser, is sufficient for this. Trying
)?
The --analyze isn't really necessary, but yeah that should do it.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
thing.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
option after a db cluster has been
instantiated? Or do I really need to rebuild postgres with the --with-libxml
parameter?
You don't need to re-initdb the database. You do need to rebuild the
executables with the correct configure options.
regards, tom lane
--
Sent
on a filesystem without largefile support. Yes, ext3 is okay, but
are you sure the customer is dumping onto ext3?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
...)
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
database mexi
vacuumdb: vacuuming of database mexi failed: ERROR: out of memory
DETAIL: Failed on request of size 134697600.
What is your maintenance_work_mem setting? It rather looks like it's
more than your system will really allow.
regards, tom lane
--
Sent via pgsql
Nicolas Michel nicolas.mic...@lemail.be writes:
Tom Lane a écrit :
What is your maintenance_work_mem setting? It rather looks like it's
more than your system will really allow.
I already tried to set the work_mem setting to the max value I can but
it changed nothing.
I did not say
to 64 bit
There are different schools of thought about that, but in any case the
difference is not likely to be large. If you want to discuss it,
pgsql-performance would be a better forum.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org
;
text
\x61626364
(1 row)
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Lewis Kapell lkap...@setonhome.org writes:
... psql contains a command \password that can be used
to safely change a role's password.
FWIW, all that's doing is pre-encrypting the password and sending
ALTER ROLE WITH ENCRYPTED PASSWORD '...';
regards, tom lane
--
Sent
.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
as something else is deleting it.
We fixed that around 8.2, but it's really just a cosmetic issue
(you'd rather the message was relation foo does not exist ...)
I don't see any reason to worry.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin
to time is push out the
wraparound limit (by freezing very old rows' XID numbers). As long as
there's a few million transactions' worth of daylight between the wrap
limit and current XIDs, there's nothing to worry about.
regards, tom lane
--
Sent via pgsql-admin mailing list
memory area set to about 1GB, and you are looking at
the output of tools that report all of that as belonging to each process
that's connected to the shared memory segment.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes
' is 0x35, just
one bit different.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
in the other table might make the
check expression no longer true, but the system wouldn't notice.
I think you might be trying to re-invent foreign keys, but without
an explanation of what it is you hope to accomplish, it's hard to
be sure.
regards, tom lane
--
Sent via pgsql
connected to those databases.
Did you pay attention to whether the restore reported any errors?
What PG version is this?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
Jan-Peter Seifert jan-peter.seif...@gmx.de writes:
I didn't see any explicit type cast in 8.3 for regprocedure - text. Is there
a way to add it in 8.2?
You can always cast pretty much anything to anything via a variable
assignment in plpgsql...
regards, tom lane
we do something like
ERROR: password authentication failed (using password from .pgpass)
ie, just tack on a comment to the error message?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http
there waiting
for notifies. (Well, it might be able to do some other useful work
too, but the simplest way is to dedicate a connection for this.)
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http
an open transaction that's older than the one that deleted
those rows (or at least started before the latter committed).
pg_stat_activity might be helpful in fingering the culprit.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make
of temp tables
in this application, that could be the problem.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
.
Put it on a machine where you do trust the admins, instead.
In commercial contexts, the more usual procedure is to put appropriate
restrictions into the contract. Warranty void if seal is broken, etc.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin
about setting it to less than 100 or so.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
of what you need to do, I'd recommend cutting
max_files_per_process to a couple hundred and upping the kernel limit
to somewhere north of 5.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http
active backends on such a restricted server. Get
yourself a connection pooler and knock down max_connections to 100 or
so.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
to have match.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
isn't going to solve it. Maybe LDAP or Kerberos?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
it?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
the config file
so it knows where the data directory is ...
Since you say you're using pg_ctl, why don't you use its -w option and
not let the script proceed until you know the postmaster is up?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org
, then go back to your last backup (I hope you've got one).
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
damaged, REINDEX will fix it, eg
reindex index pg_toast.pg_toast_17341_index;
The bigger concern is whether there is other damage. Have you had any
system crashes, indications of flaky hardware, etc on that machine?
regards, tom lane
--
Sent via pgsql-admin mailing
code.
If this can actually be reproduced in bare plpgsql, I would like to see
a complete test case.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
it.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
this is considerably slower than on the older server.
If these are indexes on textual data, maybe you accidentally changed
from C locale to some other locale. All the other ones are slower to
compare text strings, sometimes massively so.
regards, tom lane
--
Sent via pgsql-admin mailing
/local/include and /usr/local/lib automatically, but
vendor cc's usually are not.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
be the easiest fix. I'm worried to just leave it at
that, though, since if we don't identify what happened to pg_database
it's likely to happen again.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription
version.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
501 - 600 of 3437 matches
Mail list logo
