On Wed, Oct 16, 2013 at 12:04:53PM +1100, James Sewell wrote:
Let's say I'm running the following SQL script via psql -f
BEGIN
\set ON_ERROR_STOP
SELECT myFunction();
CREATE TABLE x(id int);
END;
Is there anything I can do in myFunction which will:
a) Stop execution of the script so
Carlo Curatolo wrote:
When I lauch a vacuumdb, I have an error : ERREUR: en-tête de page invalide
dans le bloc 39639 de la relation base/16384/599662
With a
SELECT * FROM pg_catalog.pg_largeobject
Result is
ERREUR: en-tête de page invalide dans le bloc 39639 de la relation
Thanks for the help.
SELECT oid, relname, relkind FROM pg_class WHERE relfilenode = 599662; --
returns nothing.
No crash occurs, I have tested the hardware (memory, harddisks, RAID5,
stability test...)
I have made a little program to read all the LargeObject of my tables, they
are all readable.
Carlo Curatolo wrote:
SELECT oid, relname, relkind FROM pg_class WHERE relfilenode = 599662; --
returns nothing.
Maybe the wrong database?
Try to find out which object this file belongs to (maybe with oid2name).
No crash occurs, I have tested the hardware (memory, harddisks, RAID5,
stability
Yes I ran pg_dumpall, create a new cluster and import.
Everything seems fine now.
How can I prevent that ?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Invalid-Page-Header-Error-tp1925403p5774728.html
Sent from the PostgreSQL - general mailing list archive at
Carlo Curatolo wrote:
Yes I ran pg_dumpall, create a new cluster and import.
Ok, cool.
Everything seems fine now.
How can I prevent that ?
Prevent data corruption?
Have good hardware, run the latest PostgreSQL fixes...
Most of all, have a good backup so that you can recover.
Yours,
I have just done an update on my Debian servers running postgresql 9.2
(Postgres is from 9.2.4-2.pgdg70+1 from apt.postgresql.org) and suddenly
can't login to postgresql as postgres with the normal peer/ident
authentication over a local Unix socket.
I've worked around it (I'm using md5 for the
On 10/16/2013 06:56 AM, Rory Campbell-Lange wrote:
I have just done an update on my Debian servers running postgresql 9.2
(Postgres is from 9.2.4-2.pgdg70+1 from apt.postgresql.org) and suddenly
can't login to postgresql as postgres with the normal peer/ident
authentication over a local Unix
All;
One of our clients is talking about moving to Mongo for their
reporting/data mart. I suspect the real issue is the architecture of
their data mart schema, however I don't want to start pushing back if I
can't back it up.
Anyone have any thoughts on why we would / would not use Mongo
On 16/10/13, Adrian Klaver (adrian.kla...@gmail.com) wrote:
On 10/16/2013 06:56 AM, Rory Campbell-Lange wrote:
I have just done an update on my Debian servers running postgresql 9.2
(Postgres is from 9.2.4-2.pgdg70+1 from apt.postgresql.org) and suddenly
can't login to postgresql as postgres
Hello
I just upgraded my postgresql server from 8.4 to 9.2 on ubuntu linux 12.04.
I installed the new version then used pg_upgrade to upgrade and replicate
the cluster from the old server to the new.
Everything appears to have worked well except that I am left with a problem
with my pg_hba.conf
On Wed, Oct 16, 2013 at 10:30 AM, CS DBA cs_...@consistentstate.com wrote:
All;
One of our clients is talking about moving to Mongo for their reporting/data
mart. I suspect the real issue is the architecture of their data mart
schema, however I don't want to start pushing back if I can't
Rory Campbell-Lange r...@campbell-lange.net writes:
Thanks for the suggestion for checking the logs. My apologies for not
checking that. The logs show:
2013-10-16 16:21:16 BST template1 LOG: local user with ID abc does not
exist
2013-10-16 16:21:16 BST template1 FATAL: Peer
On 10/16/2013 8:34 AM, Rory Campbell-Lange wrote:
I've just turned the setting in pg_hba.conf from md5 back to peer and
reloaded the server so that it now reads as:
local all postgrespeer
Attempting to log in fails with the following error on
On Wed, Sep 25, 2013 at 07:29:30PM +0400, Murat Kabilov wrote:
Hello,
I've just upgraded my database from 9.2.2 to 9.3.0 using pg_upgrade. Besides
I've updated hstore extension (alter extension hstore update).
But I can't find new to 9.2 hstore functions such as hstore_to_json in my
On 16/10/13, Tom Lane (t...@sss.pgh.pa.us) wrote:
Rory Campbell-Lange r...@campbell-lange.net writes:
2013-10-16 16:21:16 BST template1 LOG: local user with ID abc does
not exist
2013-10-16 16:21:16 BST template1 FATAL: Peer authentication failed
for user postgres
However
On Sun, Oct 6, 2013 at 11:20:14PM +0800, Patrick Dung wrote:
Noted and thanks.
I can see that it should be updated in the devel manual page:
http://www.postgresql.org/docs/devel/static/pgupgrade.html
Yes, it is updated now, it just takes a few hours.
--
Bruce Momjian br...@momjian.us
Hi,
On 17 October 2013 02:30, CS DBA cs_...@consistentstate.com wrote:
Anyone have any thoughts on why we would / would not use Mongo for a
reporting environment.
hm.. I wouldn't use anything which doesn't support rich SQL as a
backed for reporting system. In mongo, simple selects are fine but
In a new database test, I create the following table and function:
create table tb_item ( item integer );
create or replace function fn_new_item( in_item integer )
returns integer language plpgsql as
$_$
begin
insert into tb_item values( in_item );
return in_item;
end
$_$;
Then, I
By the way, I am running Postres 9.1.9.
Moshe Jacobson mo...@neadwerx.com writes:
However, It behaves as one would expect if the first CTE is built with INSERT
... RETURNING.
CTEs containing INSERT/UPDATE/DELETE are guaranteed to be executed exactly
once. CTEs containing SELECTs are guaranteed to be executed at most once
(the
On 10/16/2013 09:46 AM, Bob Jolliffe wrote:
Hello
I just upgraded my postgresql server from 8.4 to 9.2 on ubuntu linux
12.04. I installed the new version then used pg_upgrade to upgrade and
replicate the cluster from the old server to the new.
Everything appears to have worked well except
On Wed, Oct 16, 2013 at 4:26 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Moshe Jacobson mo...@neadwerx.com writes:
However, It behaves as one would expect if the first CTE is built with INSERT
... RETURNING.
CTEs containing INSERT/UPDATE/DELETE are guaranteed to be executed exactly
once. CTEs
Hi Kevin,
This might help you more
http://www.slideshare.net/nurulferdous/nosql-is-it-for-you
Cheers,
NH
.
On Wed, Oct 16, 2013 at 10:30 PM, CS DBA cs_...@consistentstate.com wrote:
All;
One of our clients is talking about moving to Mongo for their
reporting/data mart. I suspect the real
On 10/16/2013 04:20 PM, Bob Jolliffe wrote:
CCing the list so more eyes can see thid.
Hi Adrian
Sure. Here are 6 versions of complete pg_hba.conf files:
1. This works (note the auth method is peer not ident. my first post
had an error). Complete one line pg_hba.conf file:
local all
On 10/16/2013 4:56 PM, Adrian Klaver wrote:
I have never seen this http://127.0.0.1/32 in a pg_hba,conf. Of
course I don't get out much:) Not sure of its purpose. It seems to be
in the place of the IP mask.
i think thats an email program artifact, trying to treat an IP as a URL
--
john r
On 17/10/2013 00:06, Merlin Moncure wrote:
That being said, I do think it might be better behavior (and still
technically correct per the documentation) if volatile query
expressions were force-evaluated.
This sounds reasonable for a yes or no case like this, but wouldn't it
raise the
On 10/16/2013 05:03 PM, John R Pierce wrote:
On 10/16/2013 4:56 PM, Adrian Klaver wrote:
I have never seen this http://127.0.0.1/32 in a pg_hba,conf. Of
course I don't get out much:) Not sure of its purpose. It seems to be
in the place of the IP mask.
i think thats an email program artifact,
On Wed, Oct 16, 2013 at 8:30 AM, CS DBA cs_...@consistentstate.com wrote:
All;
One of our clients is talking about moving to Mongo for their
reporting/data mart. I suspect the real issue is the architecture of their
data mart schema, however I don't want to start pushing back if I can't
29 matches
Mail list logo
