ools
mature.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ollowing line in
> src/Makefile.global:
>
> LIBS = -lz -lresolv -lcompat -lm -lutil -ltermcap -lreadline
That's a good fix.
The current CVS tip also works around this problem.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
owing (completely untested):
# for local Python install
make install python_moduledir='$(pkglibdir)' python_moduleexecdir='$(pkglibdir)'
# (yes, single quotes)
# for local Perl install
make install mysterious_feature=yes
# (seriously)
--
Peter Eisentraut [EMAIL PROTECTED]
all it).
This is currently the default behaviour, if you recall. ;-)
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
eld = NULL' should also be false, but PostgreSQL treats it
as 'field IS NULL' to allow broken clients to work. See also
<http://www.de.postgresql.org/users-lounge/docs/7.1/postgres/functions-comparison.html>.
--
Peter Eisentraut [EMAIL PROTECTED] http://funk
ve left in your $PGDATA directory.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
nstalled a fix for this in the development sources; I understand
that you were able to fix this yourself.
The more interesting question is why it's trying to use on_exit() when it
should be using atexit(). If you're interested, you can try to look
through config.log to see what'
es)
LINK.shared = $(CC) -shared
else
LINK.shared = $(CC) -G
endif
else
ifeq ($(GXX), yes)
LINK.shared = $(CXX) -shared
else
LINK.shared = $(CXX) -G
endif
endif
(Or just change the -G if you don't care about generality
es not mention -209, at least in the ecpg documentation I'm looking
> at,
7.2 doesn't document it either...
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)---
TIP 5: Have you checked
Szima Gabor writes:
> Table-OID are cached and not flushed after DROP TABLE?
Something like that, but what are you expecting?
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)---
TIP 2: you
m the documentation.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
[EMAIL PROTECTED] writes:
> How can I make the transaction_code not to increase if the record is
> not added into the table?
This is a question, not a bug report.
Sequences may contain holes. If you don't want that you can't use
sequences.
--
Peter Eisentraut [EMAIL P
completely incomprehensible workaround, but since you didn't
post the exact outputs above I cannot guess what actually happened here.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
_ESE| PE_CS_I
> 252 | W_SIFITES_ESE| SD_SR_I
> 253 | |
The field separator only works in the unaligned output mode (\a).
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)
o support
it on all installations we had to give it some special treatment.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
re 'ken' > 'k, ';
# Does not work!!!
select current_time where 'kens' > 'k, P';
# Also does not work
select current_time where 'ens' > ', P';
For "Works", I mean returns a result (the where expr
Rich Morin writes:
> It is a ToC entry, looking like
>
>"12.1.7. The #random# test ... 76"
>
> where the '#'s actually show up as squares.
Those are supposed to be double quotes. It's possible that the
Microsoftish "smart quotes" snuck in
ould be on page "iii". Also,
>there seem to be two sequences of Arabic page numbers (e.g., the
>Preface is not the first item, yet it is listed as Page "i").
>
>In Table 3-10, the text is jammed up against the lefthand rules.
Peculiar.
>On page
our own choice with
CASE WHEN value THEN 'value if true' ELSE 'value if false' END
The issues are similar with numeric=>text, but the to_char() family of
functions should be able to solve all your problems in this area.
--
Peter Eisentraut [EMAIL PROTECTED]
--
Arcady Genkin writes:
> That's fine, but IMO "psql -h /var/pgsql --help" and "psql --help"
> should either both work, or both not work.
I don't think so.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
not
> clear in the docs that sysid should be positive and
> the error message is a little bit confusing.
peter=# select version();
version
-
PostgreSQL 7.0.2 on i686-pc-linux-gnu, compiled by gcc 2.96
(1
Tom Lane writes:
> Peter, what do you think of hacking psql to only try the pg_description
> actions if pset.issuper? The alternative is to invent COMMENT ON LARGE
> OBJECT, which is more work than I have time for at the moment.
Sounds reasonable.
--
Peter Eisentraut [EMAIL
> Markus Mikkolainen ([EMAIL PROTECTED]) reports a bug with a severity of 3
> java-building ant confused with xscreenhack-ant by .configure
Already fixed in 7.2.
--
Peter Eisentraut [EMAIL PROTECTED] http://funkturm.homeip.net/~peter
---(end of bro
lumn of type serial is not beeing
> droped automatically when the table containing the serial-column is
> droped. Does it make sense to store a sequence without a corresponding
> table ?
Possibly you want to use it for more than one table.
--
Peter Eisentraut [EMAIL PROTECTED] http:
xt release. If time allows please get the latest beta of PostgreSQL 7.2
from a mirror near you, test it on your platform, and send a report (good
or bad) to [EMAIL PROTECTED] so we can include it on the
"supported" list or iron out the remaining problems.
--
Peter Eise
ml#SQL-SYNTAX-IDENTIFIERS
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the m
ehaves, you
need to use "info libc".
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
"
> it wasn't always portable between OS's. Is that how we want to go?
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
ing I recall it needing is the namespace configure test,
which it already gets via pg_config.h.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
> With glibc 2.2 and linux-i386 MAX_DBL must be formated with 17 digits,
> not with 15
Says who?
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
use there is no such data type. The RAW(x) data type used elsewhere
also doesn't exist.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
/backend/access/heap/heapam.c
> cc: error 1405: "/opt/ansic/lbin/ccom" terminated abnormally with signal 11.
That is a compiler bug. Complain to your vendor.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscr
able effect.
>
> This is not a bug, but the behavior required by SQL9x afaicr.
AFAIK, this is PostgreSQL bugward compatibility. SQL says that
current_timestamp returns the "current timestamp", which you can interpret
any way you want to.
--
Peter Eisentraut [EMAIL PROTECT
f three-valued Boolean logic.)
If you want
a <> b
to return true if one of a and b is NULL and the other is not NULL then
you will have to do a bit more work. For example,
(a <> b) or (a is null and b is not null) or (a is not null and b is null)
--
Peter Eisentr
Per Winkvist writes:
> When creating a table from psql named 'tblProduct' that is turned into
> tblproduct.
Unless you double-quote it.
> However, when creating a table with the tcl/tk application pgaccess you
> can create a table that have capital letters. Isn't t
ce isn't owned by the table. It might be used elsewhere as
well.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
> It seems that it is not allowed to specify the tableowner in an SQL statement
And this is a bug exactly why?
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
h
if ((value = GetVariable(pset.vars, "ECHO")) && strcmp(value, "all")
== 0)
puts(options.action_string);
- successResult = HandleSlashCmds(options.action_string, NULL, NULL) !=
CMD_ERROR
+ successResult = HandleS
> Ignore my submission about sh-vs-bash in configure. Configure is
> still broken (doesn't set HAVE_SNPRINTF_DECL properly), and the
> resulting tree still doesn't build under IRIX with MIPSpro ($CC
> accidentally got reset to gcc between tries).
Shows us the confi
ccIdlVTM.s:7 Segmentation fault
> line: .file 1 "hashstrat.c"
>
> make[4]: *** [hashstrat.o] Error 1
If the compiler crashes then that's a bug in your compiler.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)--
> The pg_dumpall script seems to ignore the file and format switches
> that are used with pg_dump. pg_dumpall always writes to stdout in
> text format. Also, the -b switch can not be used with pg_dumpall
> since text output is being forced.
That's not a bug.
--
Peter Ei
Bruce Momjian writes:
> Peter Eisentraut wrote:
> > > The pg_dumpall script seems to ignore the file and format switches
> > > that are used with pg_dump. pg_dumpall always writes to stdout in
> > > text format. Also, the -b switch can not be used with pg_dump
/postgreSQL/source/postgresql-7.2.1/src«
gmake: *** [install] Fehler 2
Whats my mistake
mfg
peter koll
begin:vcard
n:koll;peter
tel;cell:0171 - 7941591
tel;fax:02981 - 923736
tel;work:02981 - 923712
x-mozilla-html:FALSE
url:http://www.p-a-d.de
org:p.a.d. karosserietechnik gmbh;winterberg
adr
Really? If there was a patch, I missed it.
My recollection is that there was general agreement about this
particular problem (see, for example,
http://archives.postgresql.org/pgsql-bugs/2006-04/msg00189.php ), but
things kind of trailed off after that without a resolution.
As far as the complete
>>> On 16.06.2006 at 23:21:21, in message
<[EMAIL PROTECTED]>, Bruce Momjian
wrote:
> Yea. Where you using WAL archiving? We will have a fix in 8.1.5 to
> prevent multiple archivers from starting. Perhaps that was a cause.
>
Not at the time, no. The rename in question was just a regular WAL
s
radoslaw wisniewski wrote:
> function upper combined with like opertaor and german umlauts (db
> encoding UTF8) fails.
You have probably configured the wrong locale, but you have not given
nearly enough information to reproduce your problem.
--
Peter Eisentraut
http://developer.postgres
JarosÅaw Bojar wrote:
> ILIKE operator works incorrectly with UTF8 encoding and Polish
> characters.
What does SHOW lc_collate say?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you search
be the right one.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Richard Troy wrote:
> I'm unaware of any upper case or lower case for 'ß'
It's a matter of taste whether you leave 'ß' as is or replace it by 'SS'
when upper casing. PostgreSQL does upper-casing character by
character, so there is no support for one
$(filter -lintl -lssl -lcrypto -lkrb5 -lcrypt -lm, $(LIBS))
$(PTHREAD_LIBS)
ifeq ($(PORTNAME), win32)
# Link to shfolder.dll instead of shell32.dll
SHLIB_LINK += -lshfolder
endif
Presumably the same would be necessary everywhere else libpq is used.
--
Peter Eisentraut
http://developer.pos
The following bug has been logged online:
Bug reference: 2602
Logged by: Peter Jones
Email address: [EMAIL PROTECTED]
PostgreSQL version: nonw
Operating system: noen
Description:nnnone
Details:
none
---(end of broadcast
Bruce Momjian wrote:
> One idea would be to handle C locale behavior differently from non-C
> locale.
Right.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
tters that are actually expected as answers.
I'll look into it.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
my Python installation:
> /usr/local/lib/python2.5/distutils/
That proves only that a directory by that name exists, but you haven't
shown any evidence that an importable Python module by that name
exists.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
--
produce unexpected result for column 'strange':
>
> strange | to_char | to_char
> ++
> 2005-01-01 | 2006-01-02 | 2006-01-01
This is correct. January 1, 2006 belongs to 2005 in this "ISO" way of
counting.
ear "." at character 30
You are making the faulty assumption that example.com and "example.com"
are the same thing.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: explain analyze is your friend
Delight Chen wrote:
> Initdb with SQL_ASCII is work.
If you do that, most of the encoding stuff won't work correctly. Use
some other encoding.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
T
Lachhman Dass wrote:
> In the Update statement alias must be supported
Says who?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
manoj wrote:
> how to start postgresql at startup
That is not a bug.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
The same problem exists in 8.1 too. See this thread
http://archives.postgresql.org/pgsql-bugs/2006-04/msg00177.php
Tom and Magnus tracked down a cause, but I don't think a fix was ever
implemented.
FWIW, we were bitten by the fsync problem which you noticed too.
Unfortunately we were never ab
That might be one cause (or it might otherwise exacerbate the problem),
but it isn't the only cause. We weren't running anti-virus software and
neither is Thomas. Unfortunately with the last go around, we
collectively ran out of ideas before an underlying cause could be
identified.
Pete
>>> Tom
Move to Linux. :-) In our case, everything but the database servers
were already Linux so it was an easy choice. Things have been rock
solid since then.
Once things get stuck, I don't think there is an alternative besides
"stop -m immediate". However, since the problem is caused by an idle
back
Marcio wrote:
> Is complicated encrypt the procedures/functions on Database like
> Oracle or similar?
In order to execute the code you will have to be able to read it, so
there will be no security gained by encryption.
--
Peter Eisentraut
http://developer.postgresql.org/~
The following bug has been logged online:
Bug reference: 2741
Logged by: Peter Harris
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1 and earlier
Operating system: Linux
Description:Double-free on error in ECPGconnect
Details:
When using more than one
Dave Page wrote:
> No, it's the intended behaviour. pgAdmin doesn't have any idea how
> you want to quote SET values, so it leaves it to you to add them.
Just quote them all.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(
The following bug has been logged online:
Bug reference: 2899
Logged by: Peter Hardman
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows XP Pro
Description:psql-odbc logging does not work for ordinary users
Details:
Checking MyLog
David Lloyd wrote:
> According to the ISO standard, 8601:
The date/time input format in PostgreSQL is determined by the SQL
standard, not ISO 8601.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1:
; argument type". Computing requires exactness.
Aside from the apparent discrepancy between the documentation and the
actual behavior, is there an actual use case where this is a problem?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadca
sing warning along the road, couldn't you have
> walked around that stone ?"
No, I'm asking what kind of stone it was and why it is a problem.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Tom Lane wrote:
> I'm starting to get the feeling that the entire idea of NOT NULL
> domains is broken :-(
How is that so very different from having a default value of 5 with a
domain that rejects 5?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Jessica wrote:
> Description:where is the user guide
That is a usage question, not a bug report. Perhaps you want to join
the pgsql-novices list to learn about using PostgreSQL.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadc
d "dow" fields conform to each other ?
They don't.
> If "dow" can not be changed for reasons of backward compatibility, I
> suggest a new subfield "dayofweek" that does conform to the standard.
That might be reasonable. (Or maybe "isodow".)
--
Pe
# select test2();
ERROR: query "SELECT 'select a', 'b'" returned 2 columns
CONTEXT: PL/pgSQL function "test2" line 1 at execute statement
In the presence of a comma-separated list of arguments it seems to
intepret the EXECUTE command wildly dif
y system thinks that the average of '1 day 12 hours' and '8
hours' is 22 hours, and also that the average of '2 days' and '3 days'
is 2 days and 12 hours, so it does make the assumption that 1 day = 24
hours.
--
Peter Eisentraut
http://developer.postgre
Pavel Stehule wrote:
> check constraint doesn't work correct:
There is nothing incorrect happening here. I think you are confused.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: You can help
Eli Green wrote:
> This makes it impossible to know column information for both sides of
> a foreign key.
I think the information you want is in KEY_COLUMN_USAGE.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of bro
vate library that seems to provide a similar
interface?" is a "Frequently Asked Question".
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Andrew Rass wrote:
> ERROR: IN types character varying and integer cannot be matched
> SQL Status:42804
Please provide the complete table definitions necessary to reproduce the
problem.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of bro
Michael Witten wrote:
> Now I have to issues all of these commands and follow all of these
> protocols when a simple copy should have done the trick.
What is your point? Complain to your CPU manufacturer if you don't like
how they lay out data in memory.
--
Peter Eise
Ilya Storozhilov wrote:
> 1. Create database in UTF8 encoding
You have likely forgotten to set a matching locale.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner w
, the daemon must be
running in a different directory, and there is no definite reason why you
should stop that one. It might be serving some other application.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
, it's a "\" followed by an "n". You need to actually
enter two newlines
psql -At -P recordsep="
" -U postgres -c "select generate_series(1,3)"
or figure out how your shell makes escapes available.
--
Peter Eisentraut
http://developer.postgresql.org/~pete
Jose Blanco wrote:
> This second time I did, see
>
> select author, sort_author from itemsbyauthor where sort_author like
> 'tan%' order by 2;
No, your posts didn't contain that query.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
-
The following bug has been logged online:
Bug reference: 3266
Logged by: Peter Koczan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: CentOS Linux 4.4 (RHEL 4) running on Pentium 4
Description:SSL broken pipes kill the machine and fill
ht
> ebenfalls Tabelle »...«'. löscht is like drop, and this is wrong. The
> correct sentence must to be 'Truncate-Vorgang leert ebenfalls Tabelle
> »...«'.
Fixed. Thanks.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
--
One more quick addendum...I tried this with non-SSL connections, and
this problem did *not* arise when using non-SSL connections.
Peter Koczan wrote:
Yes, #2829 seems quite similar to my plight. I did take a look through
the code tree and there appear to be checks for an EINTR status within
x27;t know enough about OpenSSL and it took me a long time to find out
as much as I did.
FYI, I compiled against OpenSSL 0.9.8d, if that makes any difference.
Peter
Magnus Hagander wrote:
This looks a lot like bug #2829 (excep that one is Windows), as I
mentioned here:
The following bug has been logged online:
Bug reference: 3504
Logged by: Peter Koczan
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: CentOS 4.5 Linux (RHEL 4), kernel 2.6.9-55.ELsmp
Description:Some listening sessions never return from
Heikki Linnakangas wrote:
Peter Koczan wrote:
There is a problem where connections listening for asynchronous notifies
occasionally block for writing on ther server side and never finish,
resulting in connections that always have the status "notify interrupt".
Apparently, this cau
Tom Lane wrote:
1Heikki Linnakangas <[EMAIL PROTECTED]> writes:
Peter Koczan wrote:
There is a problem where connections listening for asynchronous notifies
occasionally block for writing on ther server side and never finish,
Does the client read the async notifie
quick perusal of the other "notify interrupt" connections shows 13032 in
the Send-Q column. They all got into this state at the same time.
Peter
P.S. Thanks for the help, I really appreciate it.
On 8/2/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> Peter Koczan <[EMAIL PRO
ifies. They may not have happened at the same time, but it's a bit
perplexing that they all have the exact same amount of data in the queue.
Peter
On 8/2/07, Peter Koczan <[EMAIL PROTECTED]> wrote:
>
> I found something pretty interesting when running netstat's:
>
> Be
= 70400
PQfreemem(notify);
#else
Safefree(notify);
#endif
retsv = newRV(sv_2mortal((SV*)ret));
return retsv;
} /* end of dbd_db_pg_notifies */
On 8/2/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> "Peter Koczan" <[EMAIL PROTECTED]> writes:
> &g
I think the code is somehow interrupt based, but I don't know. I've
asked the primary maintainer of the program to look into this with me.
We should have more insight by early next week.
Peter
Tom Lane wrote:
"Peter Koczan" <[EMAIL PROTECTED]> writes:
This app
f the main window, so it looks
like if you have more than one main window open, update_reqs would
be called more often. That might have to be changed.
So, it looks like the app polls for async notifies every second. Hopefully
you can glean some insight from that.
Peter
On 8/3/07, Peter Kocz
hing every
second for bad connections (so notifies are being processed somehow), and it
doesn't explain why the recv-q is filling up even for good connections.
Hopefully this will help somehow, though.
Peter
P.S. Just in case its useful, the contents of pg_listener for bad
connections (I verified
On 8/6/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Peter Koczan" <[EMAIL PROTECTED]> writes:
> > Here's my theory (and feel free to tell me that I'm full of it)...somehow, a
> > lot of notifies happened at once, or in a very short period of time, to t
On 8/9/07, Peter Koczan <[EMAIL PROTECTED]> wrote:
> On 8/6/07, Tom Lane <[EMAIL PROTECTED]> wrote:
> > "Peter Koczan" <[EMAIL PROTECTED]> writes:
> > > Here's my theory (and feel free to tell me that I'm full of
> > > it)...some
e norm, and it seems odd to require a connection
to issue a notify itself before being able to read pending notifies
from another connection.
Any ideas?
Peter
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ry (It's DBD::Pg in your
> "real" case, isn't it?)
*Light bulb lights up* AhI see what's going on now.
I think I have enough information to test and fix the problem on our
end. Thank you all for your help and patience. This can be considered
resolved.
Peter
--
301 - 400 of 900 matches
Mail list logo
