[GENERAL] postgres unable to start
Hi All, one of our users killed a postgres process with kill -9 "PID" after that the DB server is not longer able to start. Here is the log: Jul 28 13:06:46 hdmisv03 postgres[7916]: [1790-1] user=,db=,host= DEBUG: 0: server process (PID 7918) exited with exit code 0 Jul 28 13:06:46 hdmisv03 postgres[7916]: [1790-2] user=,db=,host= LOCATION: LogChildExit, postmaster.c:2707 Jul 28 13:06:46 hdmisv03 postgres[7917]: [1795-1] user=,db=,host= WARNING: 01000: could not open directory "base/34728840": No such file or directory Jul 28 13:06:46 hdmisv03 postgres[7917]: [1795-2] user=,db=,host= CONTEXT: xlog redo drop db: dir 34728840/1663 Jul 28 13:06:46 hdmisv03 postgres[7917]: [1795-3] user=,db=,host= LOCATION: pgfnames, dirmod.c:323 Jul 28 13:06:46 hdmisv03 postgres[7917]: [1796-1] user=,db=,host= WARNING: 01000: some useless files may be left behind in old database directory "base/34728840" Jul 28 13:06:46 hdmisv03 postgres[7917]: [1796-2] user=,db=,host= CONTEXT: xlog redo drop db: dir 34728840/1663 Jul 28 13:06:46 hdmisv03 postgres[7917]: [1796-3] user=,db=,host= LOCATION: dbase_redo, dbcommands.c:2058 Jul 28 13:06:46 hdmisv03 postgres[7917]: [1797-1] user=,db=,host= DEBUG: 0: page 1 of relation base/35531019/35671296 is uninitialized Jul 28 13:06:46 hdmisv03 postgres[7917]: [1797-2] user=,db=,host= CONTEXT: xlog redo Insert item, node: 1663/35531019/35671296 blkno: 1 offset: 4 nitem: 1 isdata: F isleaf F isdelete F updateBlkno:11 Jul 28 13:06:46 hdmisv03 postgres[7917]: [1797-3] user=,db=,host= LOCATION: log_invalid_page, xlogutils.c:74 Jul 28 13:06:46 hdmisv03 postgres[7917]: [1798-1] user=,db=,host= PANIC: XX001: corrupted page pointers: lower = 59234, upper = 3, special = 59235 Jul 28 13:06:46 hdmisv03 postgres[7917]: [1798-2] user=,db=,host= CONTEXT: xlog redo Insert item, node: 1663/35531019/35671296 blkno: 1 offset: 4 nitem: 1 isdata: F isleaf F isdelete F updateBlkno:11 Jul 28 13:06:46 hdmisv03 postgres[7917]: [1798-3] user=,db=,host= LOCATION: PageAddItem, bufpage.c:144 Jul 28 13:06:46 hdmisv03 postgres[7916]: [1791-1] user=,db=,host= DEBUG: 0: reaping dead processes Jul 28 13:06:46 hdmisv03 postgres[7916]: [1791-2] user=,db=,host= LOCATION: reaper, postmaster.c:2238 Jul 28 13:06:46 hdmisv03 postgres[7916]: [1792-1] user=,db=,host= LOG: 0: startup process (PID 7917) was terminated by signal 6: Aborted Jul 28 13:06:46 hdmisv03 postgres[7916]: [1792-2] user=,db=,host= LOCATION: LogChildExit, postmaster.c:2727 Jul 28 13:06:46 hdmisv03 postgres[7916]: [1793-1] user=,db=,host= LOG: 0: aborting startup due to startup process failure Has anybody an idea how to fix that error ? TIA Tommaso
Re: [GENERAL] postgres unable to start
Hallo, some info: Postgres 8.4 Ubuntu 10.04.1 Linux hdmisv03 2.6.32-24-server #39-Ubuntu SMP Wed Jul 28 06:21:40 UTC 2010 x86_64 GNU/Linux and we installed Postgres through atp. The user wanted just to kill a connection from another user on a database. He did not kill the whole server process but only one connection on a single database. The filesystem and the postgres server were ok. No reboot or power interuption, however fsck was not run recently. The cluster includes about 450 databases. Perhaps too much? If we identify the corrupted database (I think the one with OID 35531019), is there a way to remove it manually from the file system? Tommaso On Thu, 2011-07-28 at 20:02 +0800, Craig Ringer wrote: > On 28/07/2011 7:51 PM, tommaso wrote: > > > Hi All, > > > > one of our users killed a postgres process with kill -9 "PID" > > after that the DB server is not longer able to start. > > > > > There is a lot of information missing from this question, though you > did include the log entries (thanks). Please see this for the rest of > the info you need: > > http://wiki.postgresql.org/wiki/Guide_to_reporting_problems > > Why did the user "kill -9" the DB, anyway? Was it perhaps not > responding for an extended period, and maybe in the "D" state in PS? > Are there / were there any messages in "dmesg" or in the kernel log > files? Perhaps related to I/O errors or file system errors? Was there > a recent fsck on the file system, a recent reboot of the server, or > recent power loss/interruption? > > -- > Craig Ringer > > POST Newspapers 276 Onslow Rd, Shenton Park Ph: 08 9381 3088 Fax: 08 > 9388 2258 ABN: 50 008 917 717 http://www.postnewspapers.com.au/
[GENERAL] OLEDB connection does not want to work. Help!!
Hi all, I am pulling my hair trying to make work an OLEDB
connection to POSTGRES.
Let me anticipate that, except for the connection string
I am using the same code (VB.NET, Oledb) that has already
proved to work fine with all the following systems:
sqlserver, Mysql, db2, access, Oracle
[to say although I know nothing about Postgres, in general I should
know how to deal with OleDb]
This one is the only one DBMS is giving me headache.
Could you please help me out to spot the problem?
I work now on XP, with VB.NET. I get connected. But, after that,
nothing seems to work.
my connection string looks like:
Me.ConnectionString = "Provider=PostgreSQL.1;Data
Source=MYDATABASE;User ID=postgres;Location=MioDb;Password='mypsw'"
Just at the very first and fundamental instruction:
OleDbConnection.GetOleDbSchemaTable(System.Data.OleDb.OleDbSchemaGuid.Provider_Types,
New Object() {Nothing, Nothing})
or any other one like:
OleDbConnection.GetOleDbSchemaTable(System.Data.OleDb.OleDbSchemaGuid.Tables,
New Object() {Nothing, Nothing, Nothing, Nothing})
I get an error. My error is:
PostgreSQL.1 failed with no error message available, result code:
E_OUTOFMEMORY(0x8007000E)
(Needless to say I have no memory problem my ram and my disk have
several Gigs free)
What do I have to do (before suicidal)?
-tom
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Re: [GENERAL] OLEDB connection does not want to work. Help!!
Hi Merlin, thanks! Yesterday I had the big honor to talk (by email) with Shachar and it seems that they (someday) will fix this fundamental issue. I tried to stress how important is to support the OleDbSchemaGuid info, as the main reason one wants to use this driver, like me, is because he is doing something that is independent of the underlying DBMS. >From my perpective an OleDb provider which has no support for that staff, is * totally useless *. That's also the reason why npgsql, which I have explored, is not fit for my purposes. In general when you have an application that needs to speak to all possible DBMS (and there are many, such as Reporting Tools or Query builders, ...), and hence rely strictly on the OleDb information, the OleDb is the only way to go (I believe). That's one of the reason of the popularity OleDb providers are gaining among programmers. Clearly DB producer tend to try to push towards proprietary solutions (see SQLconnections, OracleConnections, ...) but they will not succeed. General and common sense solution have always won. It's only matter of time. It is important that the Postgres people realize that a good OleDb provided is crucial to spread their product. Just as an example I am just waiting for their fix to provide support to Postgres users in one project of mine: http://cam70.sta.uniroma1.it/Community/ and this will certainly contribute to increase (a little) the popularity of Postgress. (But I cannot do anything to help them if they don't fix it.) And I guess there are hundred project like this going on... -Tom "Merlin Moncure" ha scritto: > On 4 Jul 2006 07:31:04 -0700, [EMAIL PROTECTED] > > sqlserver, Mysql, db2, access, Oracle > > [to say although I know nothing about Postgres, in general I should > > know how to deal with OleDb] > > > > This one is the only one DBMS is giving me headache. > > Could you please help me out to spot the problem? > > > > I work now on XP, with VB.NET. I get connected. But, after that, > > nothing seems to work. > > Use native .net driver, npgsql, or oledb wrapper for odbc and the odbc > driver. I never got the ole db driver to work either. > > Merlin > > ---(end of broadcast)--- > TIP 6: explain analyze is your friend ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [GENERAL] OLEDB connection does not want to work. Help!!
> ---(end of broadcast)--- > TIP 1: if posting/reading through Usenet, please send an appropriate >subscribe-nomail command to [EMAIL PROTECTED] so that your >message can get through to the mailing list cleanly Is this for me? I am currently using Google to post. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [GENERAL] OLEDB connection does not want to work. Help!!
Hi Merlin, as I tried to explain, I do not need just to send some sql to postgres, I am working at an higher level of abstraction, where I need the information (that must be) provided by (any) OleDb Provider > in my opinion the support for the npgsql driver is ok (not great). It > is much better than the oledb provider however. No doubt about that, but this is irrelevant for my purposes. > > In general when you have an application that needs to speak to all > > possible DBMS (and there are many, such as Reporting Tools or Query > > builders, ...), and hence rely strictly on the OleDb information, the > > OleDb is the only way to go (I believe). > > I have used basically every version of visual studio and have found > that in most cases for most uses, you will be best off with the oledb > provider for odbc drivers if you want to use such tools. Second > choice (.net only) is to use npgsql driver and typed datasets. I am NOT talking of "the oledb provider for odbc drivers": I never used it either. > > That's one of the reason of the popularity OleDb providers are gaining > > among programmers. > > ODBC is much more important standard than oledb. Here we have different opinions. I could show you a lot of things you cannot do without the OleDb functionalities, at least if you want to talk to all dbms at the same time. > True, but oledb is basically microsoft only protocol while odbc is > essentially open standard. Personally, I don't mind using specific > providers. For example, at least 50% of my development is directly > over libpq library. Nowadays every producer must have its OleDb provider. It's not an option. Moreless, like for me it not an option to write a program that does not use web services or isn't web enabled. Of course I could disregard that part. But that I would lose about 90% of my potential users (or clients). > > > It is important that the Postgres people realize that a good OleDb > > provided is crucial to spread their product. Just as an example I am > > just waiting for their fix to provide support to Postgres users in one > > project of mine: > > > > http://cam70.sta.uniroma1.it/Community/ > > > > and this will certainly contribute to increase (a little) the > > popularity of Postgress. (But I cannot do anything to help them if they > > don't fix it.) > You know, Merlin, sometimes people perpective are just different because they come from different experiences and environment. It's not matter to be right or wrong. In my experience, it is crucial the possibility to rely on the high level information provided by the OleDb protocol, because it allows to have a unique interface for any dbms in the world and to have a unique way to do things (apart the slight differences in sql dialects). This allows easy system integration. If you see for intance how DataTime works, retrieving dbms structure talking with any dbms and easily moving data from one to another, it will be clear what I mean. If I should write code that depends on the underlying DBMS, maintenance would just be impossibile and programming a real hell (it's already a hell the way it is now :) ! ) General standards have always prevailed. It's just matter of time. un caro saluto, Tommaso ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
