[BUGS] porting the PostGreSQL on the M68K platform
Dear sir, We are trying to port the PostGreSQL on the m68K platform, we've compiled it well, but failed to run it on the 54450 platform. I am wondering who we could refer to for help? Is there any commercial service that we could use for that kind of technical support? I am looking forward to hearing from you. Thanks in advance. PS: I got the information on below page http://www.postgresql.org/docs/9.3/static/supported-platforms.html Best Regards, Johnny Zhang
Re: [BUGS] porting the PostGreSQL on the M68K platform
On 12.10.2013 11:15, Zhang, Hongwei wrote: > Dear sir, > > We are trying to port the PostGreSQL on the m68K platform, we’ve > compiled it well, but failed to run it on the 54450 platform. I am > wondering who we could refer to for help? Is there any commercial > service that we could use for that kind of technical support? > > I am looking forward to hearing from you. Thanks in advance. > > PS: I got the information on below page > http://www.postgresql.org/docs/9.3/static/supported-platforms.html Hi, I'm not sure what "54450 platform" is, but if you think you found a bug on a supported platform then please submit a bug report here with as much detail as possible. What does "failed" mean, description of the hawdware etc. If you're porting PostgreSQL to a new platform (albeit similar to m68k) then there are probably more suitable lists - for example pgsql-hackers. Again, post as much info as possible. All mailing lists on postgresql.org (incl. pgsql-bugs, pgsql-hackers) are operated by community, with participants from various companies. If you decide you need a commercial support, the best place to start is probably http://www.postgresql.org/support/professional_support/ regards Tomas -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #8514: cache lookup failed for relation 421062806
On 11.10.2013 08:14, Michael Paquier wrote: > On Thu, Oct 10, 2013 at 1:24 AM, wrote: >> my postgresql running file . but sometime i found cache lookup >> failed for relation 421062806 error in postgresql log. can anyone >> tell me significant of this error. > > A relation has disappeared even if the session hold a sufficient > lock on it, ensuring that the relation have to be present. Which means it's probably something that needs to be investigated, especially if all the error messages all reference the same OID. IIRC one way to get this error was with two sessions - one accessing tables that are being dropped by the other one. However the report mentions version 8.4.0. Tejas, the first thing you should do is updating to the last 8.4.x version - i.e. 8.4.18. Now. You're missing ~4 years of bugfixes (that might even fix the one you're reporting). regards Tomas -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] porting the PostGreSQL on the M68K platform
On 10/12/2013 2:49 PM, Tomas Vondra wrote: I'm not sure what "54450 platform" is Presumably, the OP is referring to Freescale ColdFire MCF54450, one of an embedded family of 68000 like CPUs (not binary compatible, just assembler source compatible, and missing some parts of the 68000 architecture like BCD support). http://www.freescale.com/files/32bit/doc/prod_brief/MCF54455PB.pdf These are embedded processors with 32kbytes of static ram. that support 8-512MB of external DDR SDRAM. while they are typically targetted at RTOS systems, I guess they can run uCLinux, but I don't believe they have a MMU, so they can't run a 'regular' linux kernel. frankly, these don't seem like good candidates for a relational database server to me. -- john r pierce 37N 122W somewhere on the middle of the left coast -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #8515: Random 'relation "..." does not exist'
On 9.10.2013 19:35, nbudu...@gmail.com wrote: > The following bug has been logged on the website: > > Bug reference: 8515 > Logged by: Nicolas Buduroi > Email address: nbudu...@gmail.com > PostgreSQL version: 9.2.4 > Operating system: ArchLinux > Description: > > We've recently migrated an application from MySQL to Postgres and I've been > experiencing some really strange and random bugs. The application is a > pretty simple Rails application and the Postgres setup is the default one > provided by ArchLinux. > > > Basically, at some point a query, update or insert will not work and > complain about a table not existing, but that table was used without any > issue previously. Closing the running connection to the database and > reconnecting make that error disappear. Two concurrent connections (one from > a console and another from the app) could be contradicting themselves, one > giving the error and the other not. > > > This only happen on a development machine which is running version 9.2.4 of > Postgres. We've not encountered this error on our production/staging/ci > servers which are running Postgres 9.1.9 version. Hi Nicolas, can you check PostgreSQL logs? I'm not familiar with Arch Linux but I guess it might be /var/log/postgresql.log or something like that. Is there anything relevant in the logs? Can you explain what is the application doing? Can you try to prepare a simplified testcase, based on your knowledge of the app? kind regards Tomas -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #8515: Random 'relation "..." does not exist'
On 10/9/2013 10:35 AM, nbudu...@gmail.com wrote: Basically, at some point a query, update or insert will not work and complain about a table not existing, but that table was used without any issue previously. Closing the running connection to the database and reconnecting make that error disappear. Two concurrent connections (one from a console and another from the app) could be contradicting themselves, one giving the error and the other not. that sounds like a hardware/platform problem to me more than anything. maybe in memory cache is getting corrupted or something? -- john r pierce 37N 122W somewhere on the middle of the left coast -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
