Re: [HACKERS] port report: Linux SuSE 9.1

Sorry for the follow-up. That was with postgresql-8.0rc5.tar.bz2 Mikhail Terekhov wrote: Hello, ./configure --prefix=/tmp/pgsql --enable-thread-safety --with-pam --with-openssl --with-tcl --with-python --with-perl == All 96 tests passed. == Linux

[HACKERS] port report: Linux SuSE 9.1

SuSE Linux 9.1 (i586) Regards, Mikhail Terekhov ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [HACKERS] fs+sql

See http://archives.postgresql.org/pgsql-announce/2004-09/msg4.php Mikhail ---(end of broadcast)--- TIP 8: explain analyze is your friend

Re: [HACKERS] notification: pg_notify ?

se then it gives a lot - it eliminates need for polling completely. And once again, we already have this level of reliability. What exactly PG will get with this new LISTEN/NOTIFY mechanism? If the profit has so great value, let's implement it as an additional feature, not as a replacement of t

Re: [HACKERS] notification: pg_notify ?

Tom Lane wrote: > LISTEN/NOTIFY is basically designed for invalidate-your-cache > arrangements (which is what led into this discussion originally, no?). Why do you think so? Even if you are right and original design was just for invalidate-your-cache arrangements, current implementation has m

Re: [HACKERS] notification: pg_notify ?

Gavin Sherry wrote: > On Wed, 3 Apr 2002, Mikhail Terekhov wrote: >> >>Tom Lane wrote: >> >>>There is a very significant performance problem with LISTEN/NOTIFY >>>via pg_listener: in any application that generates notifications at >>>a significant

Re: [HACKERS] notification: pg_notify ?

rage of data to pass inherently > *transient* signals? If the system crashes, we have absolutely zero Because there is no other easy way to guarantee message delivery? > interest in the former contents of pg_listener (and indeed need to go > to some trouble to get rid of them). Th

[HACKERS] LOCK SEQUENCE

Hi, In my application I use 'LOCK seq'. In 7.0.2 it worked fine but in 7.1.2 Postgres complains that 'seq is not a table'. Is this (disabling to lock a sequences) an intended change? Thanks Mikhail ---(end of broadcast)--- TIP 5: Have you checked

[HACKERS] libpq.dll & psql.exe on Win32

Hi, There are two problems when compiling libpq.dll and psql.exe on Windows. I'm not sure it is the best way to fix them (see patch below.) Comments? Regards, Mikhail Terekhov Index: bin/psql/prompt.c === RCS file: /home/pro

[HACKERS] Re: WIN32 errno patch

ork correctly - I could insert and select large strings (>10k). Regards Mikhail Terekhov Index: libpq/fe-connect.c === RCS file: /home/projects/pgsql/cvsroot/pgsql/src/interfaces/libpq/fe-connect.c,v retrieving revision 1.17

[HACKERS] Re: To be 7.1.3 or not to be 7.1.3?

Is it possible to include patch for libpgtcl & tcl >8.0 in this release? Regards, Mikhail Terekhov Bruce Momjian wrote: > > > > > I have to fix my old fault in TID handling. > > > > I am able to have a cvs access now and would > > > > commit the f

Re: [HACKERS] Re: WIN32 errno patch

Tom Lane wrote: > > Mikhail Terekhov <[EMAIL PROTECTED]> writes: > > One can't just #undef errno on windows because it is defined as > > follows: > > I was wondering if Windows might play any games with errno. However, > we've had at least one in

Re: [HACKERS] Re: WIN32 errno patch

multithreaded application it is not a plain variable but call to the _errno() and after #undef errno one will lose errno completely. For the same reason it is impossible to use something like 'errno=0;'. Mikhail Terekhov Tom Lane wrote: > > Bruce Momjian <[EMAIL PROTECTED]>