UTF-8'
lc_monetary = 'de_DE.UTF-8'
lc_numeric = 'de_DE.UTF-8'
lc_time = 'de_DE.UTF-8'
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.
m_cost_limit = -1
lc_messages = 'de_DE.UTF-8'
lc_monetary = 'de_DE.UTF-8'
lc_numeric = 'de_DE.UTF-8'
lc_time = 'de_DE.UTF-8'
log_filename = 'postgresql.%Y'
mf
ops somewhere complaining about line 34587328 or similiar
- make some tail & head foo, or vi, to delete the one duplicate line
- start again...
It would be nice to have a simpler process. Could it be that the stored
procedure could cause a problem? I took all that from the SpamAssassin
On Mittwoch, 7. Februar 2007 09:45 Tony Grant wrote:
> Have any of you tested this under moderate load? If yes what issues
> need I watch out for?
No, but if you receive some answer, I'd be interested also - for the
same "no mysql" reason :-)
mfg zmi
--
// Mich
was just nervous and mixed the two
different warnings.
But I'd like to suggest changing the ERROR to WARNING for "duplicate key
violates unique constraint", as it's not serious - but it sounds like a
big problem.
Efharisto, Achilleas!
mfg zmi
--
ile fragments to files). After running a defragmenter
Does xfs have such stats, and defragmenter included? It could be a good
idea for me to use that, then. Currently I use reiserfs.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
//
imply store the vacuum command itself, but
every single operation done on the db.
If that's true, running vacuum before the base backup could be better,
as there are less WAL logs to store, making the backup smaller, right?
mfg zmi
--
// Michael Monnerie, Ing.BSc-
ace.
Databases are about 40GB now (test phase) and will be considerable more
once in production (we're using dbmail.org as mailserver then).
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key:
On Freitag, 2. März 2007 11:52 isk wrote:
> corrupt tar header found
I'd say your hardware is broken, either memory problem or disk problem.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas
binary values are
important, too.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: EA39 8918 EDFF 0A68
uot; in multilang is not unique. For
one "id", there can be several "language" values, having a text in that
language. Now in table types, I want to make sure that "textid" MUST
exist in multilang, and cannot be deleted when having references. How
would I
possible to tell postgres to split entries only after 200 chars, not
already at about 80?
200 should fit most log lines into one entry.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key
On Freitag, 29. Juni 2007 Michael Monnerie wrote:
> I have most entries split over several lines:
>
> Jun 29 19:56:40 db.xxx.xxx postgres[10640]: [5-1] DB=XXX U=XXX
> H=1.1.1.1 16854186.2190 idleLOG: Verbindungsende: Sitzungszeit:
> 0:01:22.10 Jun 29 19:56:40 db.xxx.xxx postgr
14:13:56 db1.zmi.at postgres[9596]: [3-2374]
0, 1, 1184933549)
And where could I configure to have english, not german, postgres logs?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666
course,
some selects for statistical purposes must also be possible, so not only
writes here. Any ideas?
mfg zmi
--
Michael Monnerie
it-management.at
0676 846914 666
---(end of broadcast)---
TIP 4: Have you searched our list archi
balabit.com/network-security/syslog-ng/
You might not change the running process, but for a new implementation
this could make things much easier.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// P
On Dienstag, 5. Februar 2008 [EMAIL PROTECTED] wrote:
> I need a sort where ß==ss and ä ==ae.
If you find a solution, I would be interested, too.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.id
#x27;ve ever seen for an open source project, and other projects
> should take it as a shining example of how things should be done.
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl
On Montag, 18. Februar 2008 Brian Modra wrote:
> Thats pretty much what I'm doing already but the problem is that I'm
> quickly running out of disk space on the remote server.
Then buy some disks for it, where's the problem?
mfg zmi
--
// Michael Monnerie, Ing.BSc
r without battery backup unit.
Nothing help you in a power failure then, except a good backup.
Had this with a customer - no more filesystem after reboot...
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.y
Even
RAID 1/5/6 doesn't help you here.
Doesn't mean you have the same, but from what you wrote I just wanted to
inform you that it's a fact that a single broken drive can destroy even
a RAIDs data very nasty.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http
EN, etc., used on a Linux host with hardware
RAID with write-back cache? Not sure if this is 100% safe.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s http://z
#x27;s handbook has this kind of documentation printed in it...
worthless.
But, BTW, does anybody have a good tool to show graphically the
relations between tables, and maybe even draw relations between tables
and create all necessary commands from this automatically? That would
be nice, along
, which is quite
big data in DB terms. 64bit is more efficient here.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fin
are no transmission errors. What can be done
to work around network problems? Example: when one rsync above does not
work, that log is never transmitted to the other host. Does somebody
have a sophisticated script for that?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://i
xact information. What is "huge", which Sun's do you
look at. How many transactions per second do you need, how many users,
what kind of db,
Still, even then I don't know if anybody could really help you really. I
couldn't, as we don't use any Sun&#x
test machine,
shouldn't cost more than 3000€, and it's good for a first idea how much
you need. And if it's too slow, you'll have an estimation of how much
more power you need. This can save a *lot* of money, as Sun's aren't
the cheapest iron around, so a smaller mod
e, I can only suggest running your
application on a test server. I'm far from being a specialist for
postgresql, but maybe other can help here too.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
//
late a % value, you could make RRD stats to
see it's change over time. Is there any project on this?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s http://zmi.
roll your own
> mrtg plugins. If you do, please share.
Thank you. I'll have a look at that nagios plugins.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s
ves. SAS preferred, as on SATA the
only quick disks are Western Digital Raptor (which aren't too bad,
btw).
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s
6 WD Raptors in RAID-6 on an Areca RAID, and changed it to 8x
Raptor RAID-10, that improved things.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.
or because of the
stored procedures? Normally there should be no way this can happen, so
what can cause this?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s http:/
-pc-linux-gnu, compiled by GCC gcc (GCC) 4.1.2
20061115 (prerelease) (SUSE Linux)
It's the RPM installed from openSUSE 10.2
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "
e 3.2.0 from one server and 3.2.4 from the other.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9
4729
4 | vscan| 18375 | 25829 | 2050215 | 1208229525 |
1382400 | 13268 | 1206501543 | 1208240637
(2 Zeilen)
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas
On Montag, 14. April 2008 Michael Monnerie wrote:
> > What do you mean "shared from 2 servers"? Are these two servers
> > using a shared network mount with the database files? Or do you
> > mean that these two servers connect as clients to a single Postgres
> &g
On Montag, 14. April 2008 Michael Monnerie wrote:
> problem with duplicate primary index entries...
I just got a warning in my Log:
Apr 16 01:52:19 db1.zmi.at postgres[21103]: [3-1] DB=bayes_pg_v1_dupidx
U=postgres H=[local] 48053eaf.526f VACUUM:WARNUNG:
Index »bayes_token_pkey« enth
On Mittwoch, 16. April 2008 Michael Monnerie wrote:
> problem with duplicate primary index entries...
I created the bayes db fresh, named it bayes_pg_v2 and re-relearned all
ham/spam from 3 concurrent connections into the db. No problem so far.
But I renamed the old, broken db and tried a
nt how to find out which
SELECT I must do to find the correct directory to a database? I saw it
once, but... many other things got stored in my brain in between, so I
VACUUMed that information out ;-)
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 06
settings, our
customers love it that way - no spam). So I got aware that bayes got
stupid and then I found the mess...
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s
On Montag, 21. April 2008 Monalee Bhandge wrote:
> I have Suse 10.2
rcpostgresql start
or
/etc/init.d/postgresql start
If you need to configure it, edit /etc/sysconfig/postgresql
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914
doesn't see
any problem, and destroys even the good harddisks data after the next
write, because the read data is already broken.
HTH, good luck.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.
, so I try this
first.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38
size of
> the WAL logs..?!?
> What else are "top performance related" options for the usage
> scenario I described earlier ?
http://www.postgresql.org/docs/8.3/interactive/runtime-config-resource.html
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
at would be the
format? I never did triggers.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D
" or so? Or even better it
should not create a backup file but say "to save this broken db please
recall pg_dump with --ignore-broken-db". We would have found it earlier
if the backup wouldn't have worked.
It's always good to have that kind of extra warnings, b
but I don't
know what would be the best way. Maybe a big log line like
YOUR DATABASE xxx SEEMS TO BE DAMAGED - PLEASE CHECK
such a line would jump into the eyes even on a big log, and it makes you
nervous enough to really check things.
mfg zmi
--
// Michael Monnerie, Ing.BSc---
E FUNCTION awlupdate()
AS 'UPDATE awl SET lastupdate=CURRENT_TIMESTAMP;'
LANGUAGE SQL;
CREATE TRIGGER awlupdate AFTER UPDATE ON awl FOR EACH ROW
EXECUTE PROCEDURE awlupdate();
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-manageme
GUAGE plpgsql;
CREATE TRIGGER awlupdate BEFORE UPDATE ON awl FOR EACH ROW EXECUTE
PROCEDURE awlupdate();
Thanks for your help! It's a bit complex just for an update, but it
works. :-)
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0676/846 914 666
3
times a day, for your specific workload.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A
software?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
//
com.tw/ their driver is
included in Linux kernel, and they are pretty damn fast. Change the
onboard RAM to 2GB, with the SAS 16 or 24 port controller this is the
way to have fun.
On their website is also benchmarks about different RAID levels, so you
can compare them.
mfg zmi
--
// Michael Monn
On Dienstag, 23. September 2008 Simon Riggs wrote:
> maintaining postgreSQL
Thanks for your work Peter, I hope your updates will be found on
http://download.opensuse.org/repositories/server:/database:/postgresql/
also, where the "official" updates are.
mfg zmi
--
// Michael Monn
_7" now contains 29257 row versions in 4856 pages
DETAIL: 23366 index row versions were removed.
4412 index pages have been deleted, 4412 are currently reusable.
CPU 0.00s/0.01u sec elapsed 12.14 sec.
INFO: index "dbmail_messages_8" now contains 29257 row versions in 4900 pages
DETAIL: 2
ail_messages_8" now contains 29257 row versions in 4900
pages
DETAIL: 23366 index row versions were removed.
4465 index pages have been deleted, 4465 are currently reusable.
CPU 0.00s/0.00u sec elapsed 12.35 sec.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://i
on a server with many DBs, as we have some.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED
nfo too. If you run a bayes database from
spamassassin, a single log entry can take 50+ lines. A restriction to
the number of lines, or length, would be very nice.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network
On Mittwoch 06 August 2008 Torsten Luettgert wrote:
> reindexdb dbname
> vacuumdb -f -z dbname
Just a question on this: Is the order correct or would a vacuum+reindex
be more correct?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415
On Samstag 16 August 2008 Devrim GÜNDÜZ wrote:
> http://www.pgcluster.org
Just tried it, site not reachable. Says something about a Subversion
problem. I can't find any notes about who to inform, so I try here .
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-manag
s" WHERE "physmessage_id" = $1"
for each and every delete of a row in that table. After a
REINDEX TABLE dbmail_messageblks;
everything seems to work.
Is that a bug or did I do something bad?
mfg zmi
--
// Michael Monnerie, Ing.BSc-
On Mittwoch 01 Oktober 2008 Tom Lane wrote:
> The best bet at the moment is to manually edit the pg_dump script
> to insert such a command between creating the table and loading it.
Wouldn't CLUSTER care about it, as it copies the whole table anyway?
mfg zmi
--
// Michael Monner
because I cannot send it to this list.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38
On Mittwoch 17 Dezember 2008 Michael Monnerie wrote:
> for each and every delete of a row in that table. After a
> REINDEX TABLE dbmail_messageblks;
> everything seems to work.
I was wrong, still get this error:
Dec 18 10:55:33 db2.zmi.at postgres[2816]: [112-1] DELETE:ERROR: could
On Donnerstag 18 Dezember 2008 Alvaro Herrera wrote:
> Does it persist if you close the connection and open a new one?
You're great, that worked indeed. I was a bit nervous now ;-) Thanks!
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 4
work for VACUUM/REINDEX.
Right?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E C
ential (based on that index) way. For
completely random accessed tables I skip cluster, and rely on
vacuum/reindex. Also, I think pg_toast tables cannot be clustered,
right?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel:
_1 index cannot be deleted without loosing performance? The
plain "Index Scan" could be used with _7 or _8 anyway.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key:
After all, for searching any
mailbox_idnr in that table (~234k entries) it doesn't really matter if
you use index _1 or _7, the sort is the same (if you don't care about
the other fields).
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 06
hat PG version is this?
8.3 on openSUSE 11.1: select version();
PostgreSQL 8.3.5 on x86_64-unknown-linux-gnu, compiled by GCC gcc (SUSE
Linux) 4.3.2 [gcc-4_3-branch revision 141291]
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31
bigint | not null default
(0)::bigint
internal_date | timestamp without time zone |
Indexe:
»dbmail_physmessage_pkey« PRIMARY KEY, btree (id) CLUSTER
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.i
On Mittwoch 21 Januar 2009 Alvaro Herrera wrote:
> What Postgres version is this?
8.3 again, the same server as before (openSUSE 11.1)
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP
After all, for searching any
mailbox_idnr in that table (~234k entries) it doesn't really matter if
you use index _1 or _7, the sort is the same (if you don't care about
the other fields).
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 06
o I would guess that Index _1 is redundant, and I can delete it because
the planner will use _7 instead. After all, for searching any
mailbox_idnr in that table (~234k entries) it doesn't really matter if
you use index _1 or _7, the sort is the same (if you don't care about
the ot
and more 15k SAS disks. The filesystem is not that important for
postgres.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
spans lots of AGs, high parallelism can take place
if it's well done.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
/
uldn't pg_dumpall get the same behaviour as pg_dump? It could get
that -Fc, and couldn't it be implementet as "call pg_dump for each db
and once for the system"? Why is it that different at all?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-m
g_dumpall. But again, just an idea, I don't
mind really. I'm just a sysadmin who wants things as easy as possible.
Maybe fixing pg_dumpall to include that -E is easier.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31
7;t love us, may the good Lord turn their hearts.
// And if He can't turn their hearts, may He turn their ankles
// So we'll know them by their limping.
mfg zmi
--
// Michael Monnerie, Ing.BSc.
--
Sorcerers have their magic wands:
powerful, potentially d
hours
for a vacuum to run. Now it takes 5-15 minutes.
And for your bloated table, you should also REINDEX afterwards, because
likely the index will be a mess also.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .netwo
d not access status of transaction 2299723776
DETAIL: Could not open file "pg_clog/0891": No such file or directory.
What can I do?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key:
e
> captains do that on a constant basis and PgSQL always has survived
> (more than the rest of the system anyways..)
Even with a XEN vm running PostgreSQL? Both on XFS with nobarrier mount
option? Try it, it's fun ;-)
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-man
g_dump: Die Anweisung war: COPY public.dbmail_messageblks
(messageblk_idnr, physmessage_id, messageblk, blocksize, is_header) TO
stdout;
What now?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP
essageblks;
^
What's my error?
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5
"Milen A. Radev" schrieb:
> Should be "CREATE TABLE messageblks (like dbmail_messageblks);"
Thanks, works. Ah, and now I found the bracket in the docs. There are so
many I overlooked it, maybe also because that command looks a bit strange
(like patched);
mfg zmi
--
Sent via pgsql-admin maili
"Michael Monnerie" schrieb:
> pg_dump: Fehlermeldung vom Server: ERROR: missing chunk number 0 for
> toast value 1460201 in pg_toast_1281127
> pg_dump: Die Anweisung war: COPY public.dbmail_messageblks
> (messageblk_idnr, physmessage_id, messageblk, blocksize, is_head
"Achilleas Mantzios" schrieb:
> did you reindex pg_toast_1281127?
> take a look at
> http://archives.free.net.ph/message/20080924.191644.d692f468.el.html
REINDEX TABLE pg_toast.pg_toast_1281127;
That runs now since 33 CPU minutes, using 100% with no visible I/O
happening. top says:
29687 postgr
"Achilleas Mantzios" schrieb:
>> That runs now since 33 CPU minutes, using 100% with no visible I/O
>> happening. top says:
>> 29687 postgres 20 0 605m 187m 3024 R 100 15.4 32:58.65 postmaster
>>
>> And "strace -p 29687" displays nothing. Could it be the process hangs? It
>> shouldn't take
"Achilleas Mantzios" schrieb:
>> That runs now since 33 CPU minutes, using 100% with no visible I/O
>> happening. top says:
>> 29687 postgres 20 0 605m 187m 3024 R 100 15.4 32:58.65 postmaster
>>
>> And "strace -p 29687" displays nothing. Could it be the process hangs? It
>> shouldn't take
"Michael Monnerie" schrieb:
> select * from dbmail_messageblks where messageblk_idnr not in (3904492);
>
> That helps. Slowly I may be able to find all broken entries. Is there a
more
> automated way?
Now I already have
select * from dbmail_messageblks where
"Michael Monnerie" schrieb:
> Now I already have
> select * from dbmail_messageblks where messageblk_idnr not in
> (3904492,3904495,3904496,3904499,3904500,3904501,3904503);
> ERROR: unexpected chunk number 1 (expected 0) for toast value 1460210 in
> pg_toast_1281127
&g
News! The server even crashes when accessing certain messageblks:
The "physmessage" table contains mails with date, mails are stored in pieces
in "messageblks" (see ER model at
http://www.dbmail.org/dokuwiki/doku.php?id=er-model ). I try to find first
and last message with a problem, here the last
I have the impression I'm asking the wrong things. Still I try.
Could I do something about this?
psql:/tmp/x:119: ERROR: invalid page header in block 973698 of relation
"pg_toast_1281127"
It seems that toast table got truncated after host+XEN crash and XFS
recovery. Would adding some zeroes to t
Is there a
smart way to do such a select without caching the results in memory? Is
that what temporary tables and "select into" are made for? I just want
to know the recommended way for doing huge queries.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http:
crash recovery startup time?
If someone is interested, I have a full postgres log with every single
command done to the database.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: &qu
eturns integer AS $$ BEGIN insert into dbmail_mailboxes
(owner_idnr,name) values (user_idnr,'INBOX'), (user_idnr,'Gesendete
Objekte'), (user_idnr,'Entwürfe'), (user_idnr,'Junk'),
(user_idnr,'Papierkorb'); END; $$ LANGUAGE plpgSQL;
But I don't
d pg_dump -T broken_table, and got all others out.
Thanks to Murphy's Law that one broken table was the biggest, the one
containing the e-mail data.
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.
blem, latest at the moment the
first transaction touched the problematic table. Instead of throwing the
data effectively to /dev/null :-(
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key:
eate the index?
That's a foreign key, if I understand you correctly.
ALTER TABLE ONLY B
ADD CONSTRAINT B_prefix_fkey FOREIGN KEY (prefix) REFERENCES
A(prefix) ON UPDATE CASCADE ON DELETE CASCADE;
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 /
y.html
http://scale-out-blog.blogspot.com/2009/02/simple-ha-with-postgresql-point-in-time.html
mfg zmi
--
// Michael Monnerie, Ing.BSc- http://it-management.at
// Tel: 0660 / 415 65 31 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | g
1 - 100 of 137 matches
Mail list logo
