Re: [BUGS] xlog lockup patch (was: BUG #2712: could not fsync
Hi. On Mon, 20 Nov 2006 15:33:33 -0500 (EST) Bruce Momjian <[EMAIL PROTECTED]> wrote: > Thomas H. wrote: > > me wrote: > > > i've loaded 1gb of data without any xlog-problems, whereas with the 8.2b2 > > > executable it locked up after ~100mb. the xlog-files are cycling... > > > > > > if i need to test for some specific behaviour let me know. > > > > what's the status on this patch for inclusion in future 8.2 builds? would > > be > > nice to see it in b4 or rc1... > > This was fixed the day after we packaged beta3: > > revision 1.44 > date: 2006/11/08 20:12:05; author: tgl; state: Exp; lines: +20 -48 > Change Windows rename and unlink substitutes so that they time out after > 30 seconds instead of retrying forever. Also modify xlog.c so that if > it fails to rename an old xlog segment up to a future slot, it will > unlink the segment instead. Per discussion of bug #2712, in which it > became apparent that Windows can handle unlinking a file that's being > held open, but not renaming it. > > beta4 will have the fix. Are there any plan to backport this patch for 8.1/8.0 server ? My customer has same problem in 8.1.5 , but this bug doesn't seems to be fixed in 8.1.6 . Backport patch for 8.1.6 attached. Sorry for replying old mail. -- TANIDA Yutaka <[EMAIL PROTECTED]> 81_win_xlog_lockup_fix.patch Description: Binary data ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [pgsql-patches] [BUGS] xlog lockup patch (was: BUG #2712:
It was considered too risky to backpatch because we couldn't do sufficient testing. --- TANIDA Yutaka wrote: > Hi. > > On Mon, 20 Nov 2006 15:33:33 -0500 (EST) > Bruce Momjian <[EMAIL PROTECTED]> wrote: > > > Thomas H. wrote: > > > me wrote: > > > > i've loaded 1gb of data without any xlog-problems, whereas with the > > > > 8.2b2 > > > > executable it locked up after ~100mb. the xlog-files are cycling... > > > > > > > > if i need to test for some specific behaviour let me know. > > > > > > what's the status on this patch for inclusion in future 8.2 builds? would > > > be > > > nice to see it in b4 or rc1... > > > > This was fixed the day after we packaged beta3: > > > > revision 1.44 > > date: 2006/11/08 20:12:05; author: tgl; state: Exp; lines: +20 -48 > > Change Windows rename and unlink substitutes so that they time out after > > 30 seconds instead of retrying forever. Also modify xlog.c so that if > > it fails to rename an old xlog segment up to a future slot, it will > > unlink the segment instead. Per discussion of bug #2712, in which it > > became apparent that Windows can handle unlinking a file that's being > > held open, but not renaming it. > > > > beta4 will have the fix. > > Are there any plan to backport this patch for 8.1/8.0 server ? > > My customer has same problem in 8.1.5 , but this bug doesn't seems to > be fixed in 8.1.6 . > > Backport patch for 8.1.6 attached. > > Sorry for replying old mail. > > -- > TANIDA Yutaka <[EMAIL PROTECTED]> [ Attachment, skipping... ] > > ---(end of broadcast)--- > TIP 2: Don't 'kill -9' the postmaster -- Bruce Momjian [EMAIL PROTECTED] EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 6: explain analyze is your friend
[BUGS] Bugreport
I am compiling postgres on a intel mac machine ../../../../src/include/storage/s_lock.h:543:2: error: #error PostgreSQL does not have native spinlock support on this platform. To continue the compilation, rerun configure using --disable-spinlocks. However, performance will be poor. Please report this to [EMAIL PROTECTED] In file included from ../../../../src/include/storage/spin.h:50, from xlog.c:35: -- Portrix.net z. Hd. Marco Behnke Stresemannstr. 375 22761 Hamburg ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[BUGS] BUG #2878: does not install
The following bug has been logged online: Bug reference: 2878 Logged by: kalyan Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.1 Operating system: Windows XP 64 Description:does not install Details: The binary does not install. Any plans for a 64-bit version? ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[BUGS] BUG #2876: problems witih pg_ctl -w
The following bug has been logged online: Bug reference: 2876 Logged by: Marvin Solomon Email address: [EMAIL PROTECTED] PostgreSQL version: 8.2.1 Operating system: Windows XP Description:problems witih pg_ctl -w Details: The "-w" option to pg_ctl on Windows systems has a couple of problems. The main problem is that it attempts to detect whether the server is running by establishing a session, but provides no way to supply a user name for that attempt. The default is to use your login name, but that may not correspond to any user name in the database. Here's an example: % pg_ctl start -w -l log waiting for server to start...^C % cat foo LOG: database system was shut down at 2007-01-10 05:56:57 CST LOG: checkpoint record is at 0/34ACBE0 LOG: redo record is at 0/34ACBE0; undo record is at 0/0; shutdown TRUE LOG: next transaction ID: 0/686; next OID: 16572 LOG: next MultiXactId: 1; next MultiXactOffset: 0 LOG: database system is ready FATAL: role "solomon" does not exist FATAL: role "solomon" does not exist FATAL: role "solomon" does not exist FATAL: role "solomon" does not exist LOG: received fast shutdown request LOG: shutting down LOG: database system is shut down I note that the code explicity checks for the error "no password supplied", but not for "role does not exist". Another problem is that the max time to wait is wired in at 60 seconds. It would be nice if there were some way to supply a different value. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[BUGS] FATAL: could not reattach to shared memory (Win32)
Hey, I have problem: OS: Win XP, SP2, Finnish, latest Updates Latest PostgreSQL I get every minute to eventlog: FATAL: could not reattach to shared memory (key=5432001, addr=017A): Invalid argument LOG: unrecognized win32 error code: 487 By, Mika ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[BUGS] BUG #2877: Caused by: org.postgresql.util.PSQLException: Unknown Response Type
The following bug has been logged online: Bug reference: 2877 Logged by: Ravalison Frederyk Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: win 2003 Description:Caused by: org.postgresql.util.PSQLException: Unknown Response Type Details: Sometimes in my J2EE web application, I have the following problems: Caused by: org.postgresql.util.PSQLException: Unknown Response Type at org.postgresql.core.QueryExecutor.executeV3(QueryExecutor.java:192) at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:100) at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:43) at org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.j ava:517) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.j ava:50) at org.postgresql.jdbc1.AbstractJdbc1Statement.executeQuery(AbstractJdbc1Statem ent.java:233) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:139) at org.hibernate.loader.Loader.getResultSet(Loader.java:1669) at org.hibernate.loader.Loader.doQuery(Loader.java:662) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.ja va:224) at org.hibernate.loader.Loader.loadCollection(Loader.java:1919) ... 50 more The Unknown Response Type will change each page load. To resolve the probleme, I have to restart Jonas. My configuration: Jonas 4.5.3 pg74.216.jdbc3 Postgres 8.1 Thanks ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
[BUGS] follow-up: problems with pg_ctl -w
[This is meant to be a follow-up of a bug report I sent earlier using the web form. It's not clear to me the right way to post a follow-up, since I didn't get a copy of the email generated by the web form, and the email hasn't shown up on the pgsql-bugs web site -- at least not yet.] I subsequently discovered that setting PGUSER in the environment gets around the first problem I mentioned, so it's really just a documentation problem: PGUSER is not mentioned on the pg_ctl doc page. But I found a worse problem. Sometimes (not repeatably), pg_ctl start -w logs the message FATAL: the database is starting up and immediately returns. I believe the correct thing for it to do when it gets this message from an attempt to open a session is to try again. Instead, it returns as if the startup was successful. ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [BUGS] BUG #2878: does not install
On Wed, Jan 10, 2007 at 05:18:28PM +, kalyan wrote: > > The following bug has been logged online: > > Bug reference: 2878 > Logged by: kalyan > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.2.1 > Operating system: Windows XP 64 > Description:does not install > Details: > > The binary does not install. What is the problem? I have run the binary on XP 64 without problems, though not from the MSI installer. It certainly *works*. > Any plans for a 64-bit version? There are no firm plans for a Win64 version, but we'll get there eventually ;-) We are doing some of the work needed to get there, such as updating the build system for Visual C++ 2005, on the way to 8.3, but it's impossible to say when we'll have an actual 64-bit version. //Magnus ---(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
Re: [BUGS] Bugreport
Marco Behnke wrote: > I am compiling postgres on a intel mac machine > > ../../../../src/include/storage/s_lock.h:543:2: error: #error PostgreSQL > does not have native spinlock support on this platform. To continue the > compilation, rerun configure using --disable-spinlocks. However, > performance will be poor. Please report this to [EMAIL PROTECTED] > In file included from ../../../../src/include/storage/spin.h:50, > from xlog.c:35: what versions of MacOSX and postgresql are that exactly ? Stefan ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] BUG #2877: Caused by: org.postgresql.util.PSQLException:
Ravalison Frederyk wrote: > The following bug has been logged online: > > Bug reference: 2877 > Logged by: Ravalison Frederyk > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.1 > Operating system: win 2003 > Description:Caused by: org.postgresql.util.PSQLException: Unknown > Response Type > Details: > > Sometimes in my J2EE web application, I have the following problems: > Caused by: org.postgresql.util.PSQLException: Unknown Response Type > at org.postgresql.core.QueryExecutor.executeV3(QueryExecutor.java:192) > at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:100) > at org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:43) > at > org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.j > ava:517) > at > org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.j > ava:50) > at > org.postgresql.jdbc1.AbstractJdbc1Statement.executeQuery(AbstractJdbc1Statem > ent.java:233) > at > org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:139) > at org.hibernate.loader.Loader.getResultSet(Loader.java:1669) > at org.hibernate.loader.Loader.doQuery(Loader.java:662) > at > org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.ja > va:224) > at org.hibernate.loader.Loader.loadCollection(Loader.java:1919) > ... 50 more > > The Unknown Response Type will change each page load. To resolve the > probleme, I have to restart Jonas. > > My configuration: > Jonas 4.5.3 > pg74.216.jdbc3 > Postgres 8.1 you might want to try to upgrade the JDBC driver - if i read http://jdbc.postgresql.org/download.html correctly pg74.216.jdbc3 is not the version that should be used against a 8.1 backend. Stefan ---(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
Re: [BUGS] Bugreport
Marco Behnke <[EMAIL PROTECTED]> writes: > I am compiling postgres on a intel mac machine > ../../../../src/include/storage/s_lock.h:543:2: error: #error PostgreSQL > does not have native spinlock support on this platform. Use something newer than PG 7.4, or if you must, hack up src/include/port/darwin.h to know about darwin-on-intel. regards, tom lane ---(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
Re: [BUGS] BUG #2878: does not install
On Wed, Jan 10, 2007 at 09:18:25PM +0100, [EMAIL PROTECTED] wrote: > thanks. Let me clarify - the installer does not work. I install as an admin > and > explicitly created a postgres admin account also, but it says the directory > security settings dont allow etc. Also, once I try it, I am not able to > delete the directory it > creates. > > What are my options? > K. Again, what exactly does it show you? I doubt this is because of 64-bit windows, but it's not impossible thatis. When you say you created a postgres admin account, I assume you mean a *non*-admin account? Postgres is supposed to have a non-admin account to run from. //Magnus ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
