estion. The architecture doesn't allow
it.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 8: explain analyze is your friend
stig erikson wrote:
> by the way, can i enable table compression in some way?
> i could not find it in the manual, found only compression for backups
> and EXTENDED column storage, but nothing for integers.
No, you can't compress fixed-length data types using the TOAST
mechani
Josh Berkus wrote:
> My vote is get rid of it and replace it with a DOMAIN of NUMERIC.
How would that domain be defined?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: don't forget to incre
use locales and unicode, he needs to run two instances
of postgres. One for his unicodedatabases on one for its standard
databases to get correct sorting in his locale.
GREAT JOB !! THNX A LOT !!
peter
--
mag. peter pilsl
goldfisch.at
IT-management
tel +43 699 1 3574035
fax +43 699 4 3574035
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 8: explain analyze is your friend
y a newer
version.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
le interface to match locale encodings to PostgreSQL's
encoding names.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
PostgreSQL Bugs List wrote:
> SQL Update command does not follow the order of a WHERE field IN
> subselect.
What could possibly have given you the idea that it should?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of bro
stalling everything in private directory trees and then symlinking
the relevant parts to shared locations. Also, sites using AFS file
systems do things of that kind. I hope these systems aren't going to
be broken completely.
--
Peter Eisentraut
http://develope
PostgreSQL Bugs List wrote:
> plPHP can't understand postgresql boolean...
We do not maintain or distribute plPHP. Please report problems to where
you got it from.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of b
Tom Lane wrote:
> Peter, it was you that committed the current contents of
> config/perl.m4; do you recall why it wants to remove ccdlflags from
> the Embed results?
The ldopts value contains compiler-specific shared library linking flags
plus information about additional library t
John Hansen wrote:
> On occasion, it seems the psql history file gets truncated.
Truncated to 500 lines by any chance?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: don't forget to increase y
s
> set to "traditional-chinese" literally. Shouldn't it be
> zh_TW?
That depends on what locale names the Windows operating system
understands.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
will
compare them thinking they are Big5 (or whatever) strings, which will
result in the random behavior you observed. You need to set an
appropriate locale so that the operating system also thinks they are in
Unicode.
> Are you using the locale routines in mingw?
I believe we do.
--
eady been corrected.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message
Should I be able to
compile with gcc 3.3.2 (from sunfreeware) on solaris 10?
I'm using sparc, and
am getting some strange looking compiler errors when trying to do the
make.
I'm getting some
compiler parse errors when compiling exec.c.
make -C doc
allmake[1]: Entering directory
`
there's either something bogus about the gcc for solaris 10, or perhaps there's a way to get gcc to ignore the gcc version, and use the 'normal' version..?
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 12, 2004 12:04 AM
27;t tried executing it yet, but at least it's built without complaints.
Thank you for your help.
regards,
Peter.
-Original Message-
From: Mike Mascari [mailto:[EMAIL PROTECTED]]
Sent: Saturday, December 18, 2004 5:03 AM
To: Tom Lane
Cc: Belbin, Peter; [EMAIL PROTECTED]
Sub
t does seem, to me, to be a gcc problem.
I could try building gcc myself, but, that won't fix the problem with the version on the sunfreeware site, which a lot of people rely on, I expect.
Regards,
Peter.
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Sat
e a
different editor.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Robert Sussland wrote:
> python, etc. are possible to build. running the configure script with
> the options ./configure --with-perl
>
> results in an appparently successful configure, but make returns an
> error.
Telling us which error would help a lot.
--
Peter
Andrew Kompaneev wrote:
> On Windows platform in database with encoding='UNICODE' sort order on
> column with non-english chars (for example, Cyrillic) doesn't work
Unicode doesn't work on Windows right now. Sorry.
--
Peter Eisentraut
http://develo
resql.org/docs/7.4/static/indexes-opclass.html
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
aim that
this is a bug in your frontend driver.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
to "inity", and not to the end of the input as expected.
Yes, we have seen this type of misbehavior before. It may be time to
upgrade your operating system.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)
Logvinov D. wrote:
> There are no ways to select unicode codepage during installation.
Unicode doesn't work correctly on Windows. That's why the choice is not
given during installation.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end
no one ever noticed that LOAD isn't. On a platform where that can
> execute initialization functions this does seem like a security
> issue.
I believe all ELF platforms fall into that category.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---
erred thing is to set -rpath within the executable, which
> we do already (see Makefile.solaris).
The problem with that is that it doesn't take effect for the run-time
tests run within configure.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broad
ser, the second \ is
the escape character for the LIKE pattern.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Tim Larson wrote:
> Required lib installed at /usr/include/openssl/ssl.h, but ./configure
> step still fails all three tests for it.
But without showing us the complete details, we won't be able to fix it.
--
Peter Eisentraut
http://developer.postgresql.
bout
it.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
re curious.
> Is there any possibility to set a timeout for the lock, after which the
> ALTER TABLE statement fails, instead of remaining in wait status (when
> calling with JDBC?
Yes, there is a statement_timeout parameter or something like that.
--
Peter Ei
Anthony COMMUNIER wrote:
> The statement : EXEC SQL DELETE FROM WHERE CURRENT OF
> (describe in SQL 99) isn't recognize by ecpg
PostgreSQL does not implement the entire SQL standard by any means.
Please refer to the documentation about what you can expect to work and
how.
--
The following bug has been logged online:
Bug reference: 1514
Logged by: Peter Newman
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: Fedora Core 3
Description:Inheritance and Primary Keys
Details:
Hi
Just exploring the use of
The following bug has been logged online:
Bug reference: 1528
Logged by: Peter Wright
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7, 8.0.1
Operating system: Debian Linux (unstable)
Description:Rows returned that should be excluded by WHERE clause
Details
e cases - and so the
initial "bug" I reported is technically the correct behaviour(?).
Okay, maybe I'm not completely sure I've understood you correctly. :)
On 08/03 03:07:13, Tom Lane wrote:
> "Peter Wright" <[EMAIL PROTECTED]> writes:
> > Descript
ined ANSI/ISO label. Nevertheless, referring to ISO
seems more appropriate.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
The following bug has been logged online:
Bug reference: 1555
Logged by: Peter Cottingham
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7-3.FC3.1
Operating system: Linix
Description:bug in GROUP BY?
Details:
Appears that the GROUP BY clause is not
ould work the same on all platforms, shouldn't it?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
The following bug has been logged online:
Bug reference: 1801
Logged by: Peter Valach
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux (Gentoo)
Description:pg_dump dumps tables in alphabetical order, not as
created
Details:
When
I just installed postgres from the postgresql-8.0.3.zip file, and I'm
running
XPpro. The installation seemed to go ok but when I try to login as postgres
it tells me...
psql -Upostgres -W
(I enter my password)
psql server closed the connection unexpectedly
this probably means the server termin
ign
somewhere, because in spite of this not being a bug, people will
probably consider it so and keep bothering us about it.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ST1', it will not allow me
> insert another row with 'TEST' as the value for this column.
Please show the exact sequence of commands that leads to this situation.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)-
but neither
> -lreadline or -lcurses is applied when linking psql so it fails to
> link. Manually adding -lreadline -lcurses while linking pgsql results
> in a successful link, possibly with reduced functionality.
Again, please provide config.log and the build log for analysis.
--
Bob Friesenhahn wrote:
> Using GCC 4.0.1 on Solaris 9 the configure test for isinf incorrectly
> detects success so postgres does not link.
Please provide the config.log file and the tail end of the failing build
log (at least the failing command and the error message).
--
Peter Eise
t"
> /usr/include/sys/ipc.h:56: error: parse error before '}' token
Evidently, you need to include another header before sys/ipc.h, namely
the one that defines the cid_t type. Care to find out which one that
is?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
t there are
> actually two bugs in the build but the build terminates due to the
> isinf bug. The failure to link due to -lreadline needing -lcurses
> does not occur until later.
In the logs you sent, configure decides to use -ledit, which is
something different altogether.
--
P
for each operation
the privileges that are ordinarily required for that operation. If you
want to have the function executed with the effective privileges of its
owner, you can specify the clause SECURITY DEFINER when creating the
function.
--
Peter Eisentraut
http://developer.postgresql.or
Am Dienstag, 4. Oktober 2005 14:58 schrieb Tony Marston:
> As an example, in the view "information_schema.columns" I can only see the
> entry in COLUMN_DEFAULT if I am the owner. Why is this?
Because the SQL standard says so.
--
Peter Eisentraut
http://developer.postgr
apparently dropped in SQL 2003. Clearly, we need to review the
information schema for SQL 2003 conformance.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 6: explain analyze is your friend
al changes across the board that need to be attacked as
a whole.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
al definition below. If
we followed your reading of the standard, the view would simply give
the names of the columns along with table and schema name and that's
all.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
warning: 'Int_yy_flex_free' was used with no prototype before its definition
make[3]: *** [bootparse.o] Error 1
make[2]: *** [bootstrap-recursive] Error 2
make[1]: *** [all] Error 2
make: *** [all] Error 2
ether.
Thanks all for input,
Pete
Peter Bazeley, M.Sc.Database Specialist / ResearchBioinformatics and Proteomics / GenomicsMedical University of OhioToledo, Ohio 43614-5806>>>Tom Lane <[EMAIL PROTECTED]&g
erver does not match
the database encoding. Please send us the output of
SHOW lc_ctype;
SHOW server_encoding;
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
Am Freitag, 21. Oktober 2005 17:31 schrieb Jari Aalto:
> This ONE BIG file will help loading it off-line to
> a web browser (or editor *.txt), and to make quick searches on backward and
> forward.
This wouldn't be hard to implement. Are others interested in this?
---(end
Am Montag, 24. Oktober 2005 20:27 schrieb Devrim GUNDUZ:
> I thought we do? Our RPMs are marked as PGDG RPMs...
You can also mark them "gentoo", but RPM bugs should still ideally be reported
to the RPM builder, not this forum.
---(end of broadcast)
Am Samstag, 29. Oktober 2005 02:36 schrieb Martin Pitt:
> The PostgreSQL manpages currently do not quote the dash (they contain '-'
> instead of '\-', as mandated by manpages). Since this produces a different
> Unicode character than an quoted dash, these manpages look a bit weird on
> some locale/
ass"
You need to mention pg_class in the FROM clause.
> This query worked fine with 8.0.3.
The query was always incorrect, and 8.1 is now stricter in that regard.
To get bugward-compatible behavior, look up the configuration parameter
add_missing_from.
--
Pe
HOTTA Michihide wrote:
> - N_("change a database role"),
> + N_("change a database user account"),
[etc]
The current code is correct. User accounts and groups are now mapped to
database roles.
--
Peter Eisentraut
http://develo
e. I hope that is logical enough for
you. :)
In general, if you disagree with a plan choice, you should provide
evidence that the chosen plan is in practice worse then the one you
would have preferred.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end
Jacques Grelet wrote:
> Since version 8.0.4, all French Postgresql messages are bad encoded.
Yes, the file is encoded in UTF-8 but declared to be ISO-8859-1.
Guillaume, can you check what is going on?
--
Peter Eisentraut
http://developer.postgresql.org/~pet
e patch message or release note
entry really isn't that much to ask for that service.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Am Mittwoch, 21. Dezember 2005 08:21 schrieb Martin Pitt:
> However, if --bindir etc. cannot be set, then maybe configure should
> not offer these options?
They can be set and support for that will not go away. But if you choose
unfortunate combinations of locations, the installation becomes
un
eclare a feature
intesting.
(Certainly the test suite failure should be fixed, but I don't consider
making arbitary installations relocatable as necessary or restricting
arbitrary installations as acceptable.)
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
-
t inside the substring function not trigger the end of
> comments.
The SQL standard does not provide for this kind of exception, so there
is no real use in discussing it.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)--
Am Mittwoch, 11. Januar 2006 22:33 schrieb Tom Lane:
> I suppose though that there's some chance of the constant-argument case
> being treated differently from not-constant, so your idea has some merit.
Use a global rather than a local variable.
--
Peter Eise
did like François' idea of using argc, but the present autoconf
> infrastructure doesn't seem to allow it :-(
Maybe their use is unportable. :-)
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP
're aware of it.
> pAlso on a similar note, you can't group by any
> column you don't select.
Sure you can.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading
n "basedir"
> violates not-null constraint
> Insert NULL via bind was disallowed, OK
>
> # Cut
>
> You can clearly see that inserting the empty string via do("INSERT
> ...") is correctly rejected, but performing the same insert via
> prepare/execute with bin
at doesn't make a difference.)
However, in the server logs I just see this:
FATAL: database "'tcp:postgresql://bell.credativ.de:5432/pei'" does not exist
So apparently this URL parsing needs work.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
-
The following bug has been logged online:
Bug reference: 2233
Logged by: Peter Stys
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: MacOSX
Description:Not a bug - trying to make a donation
Details:
This is not a bug report. PostgreSQL is
but 0 isn't the
one for you.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
The following bug has been logged online:
Bug reference: 2271
Logged by: Peter laursen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3.1
Operating system: Win XP SP2 Home - Dansih
Description:no privilege to install
Details:
I installed 8.1.1.1
Evgeny Gridasov wrote:
> It cannot be modified setting it in postgresql.conf (creation db
> constant?) Should I reinit database to get this working or what?
Yes.
> If I should reinit db, what locale should I choose?
Something like ru_RU.utf8.
--
Peter Eisent
prabu wrote:
> i want to store a image in the database and display it in jsp page.
That is not a bug.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
le
doing source installations.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
e PostgreSQL source distribution.
So, if there is a problem with the start script in contrib, let's fix it, but
I think it's obvious that the Red Hat RPM start script should remain just
that.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end o
Mikael Carneholm wrote:
> This seems to be a psql(?) bug:
It seems you're using an older version of psql.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 5: don't forget to increase your f
er for SIGPIPE seems very difficult.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so tha
matching. In practice, there is hardly a
reason to have LC_COLLATE and LC_CTYPE be different, so the problem
should not be that big.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 1: if posting/reading
The following bug has been logged online:
Bug reference: 2381
Logged by: Peter Krauss
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Linux
Description:LIMIT 1 very very lazy than without
Details:
The single query (on psql) is fary fast
Hi all,
We were bitten by this same bug over the weekend (PG 8.1.3 / Windows
Server 2003). The exact error was:
FATAL: semctl(170688872, 6, SETVAL, 0) failed: A non-blocking socket
operation could not be completed immediately.
The start of the errors corresponded to a nightly "vacuum analyze"
Sorry about the delay in responding. We had a bit of difficulty with
the test machine. Kevin is also on vacation this week.
The problem is repeatable with a VACUUM. I've found the offending
block. A (partial) pg_filedump of that block is pasted in below. I'm a
little lost as to what the next
2 = 635
(gdb) print rightsib
No symbol "rightsib" in current context.
(gdb) print nextoffset
$3 = 87
(gdb) print leftsib
$4 = 636
(gdb) print rightsib
No symbol "rightsib" in current context.
(gdb) continue
Continuing.
Program exited with code 03.
(gdb)
Pete
>>> Tom
The index data isn't sensitive, but I should ask for permission
nonetheless. I'll send over the '-f' output tomorrow morning.
Pete
***
* PostgreSQL File/Block Formatted Dump Utility - Version 8.1.1
*
* File: 180571
* Options used:
Also, when I tried to run a database-wide VACUUM ANALYZE VERBOSE it
actually doesn't even get to Panel and errors out with:
INFO: analyzing "public.MaintCode"
INFO: "MaintCode": scanned 1 of 1 pages, containing 19 live rows and 0
dead rows; 19 rows in sample, 19 estimated total rows
ERROR: dupl
| S02
WA| R | Warrant issued| t |
10 | t | F | S04
(19 rows)
bigbird=#
>>> Tom Lane <[EMAIL PROTECTED]> 04/12/06 5:00 am >>>
"Peter Brant" <[EMAIL PROTECTED]> writes:
>
I can't find any duplicates?!?
The query
select starelid, staattnum, ctid, xmin, xmax, cmin, cmax
from pg_statistic p1
where (select count(*) from pg_statistic p2 where
p1.starelid = p2.starelid and p1.staattnum = p2.staattnum) > 1
doesn't turn up anything. Nor does dumping
select starelid,
Per the DBAs, there hadn't been any recent crashes before last Thursday.
A "vacuum analyze verbose" discovered the problem early Thursday
morning. After the PANIC, the database never came back up (the
heap_clean_redo: no block / full_page_writes = off problem).
One thing that seems strange to me
The middle tier transaction log indicates this record was inserted into
the county database at 2006-03-31 21:00:32.94. It would have hit the
central databases sometime thereafter (more or less immediately if all
was well).
The Panel table contains some running statistics which are updated
frequen
It turns out we've been getting rather huge numbers of "Permission
denied" errors relating to fsync so perhaps it wasn't really a precursor
to the crash as I'd previously thought.
I've pasted in a complete list following this email covering the time
span from 3/20 to 4/6. The number in the firs
Sounds good.
There is nothing sensitive in DbTranImageStatus_pkey so if you decide
you want it after all, it's there for the asking.
Pete
>>> Tom Lane <[EMAIL PROTECTED]> 04/13/06 3:30 am >>>
Oh, never mind ... I've sussed it.
---(end of broadcast)--
The culprit is CLUSTER. There is a batch file which runs CLUSTER
against six, relatively small (60k rows between them) tables at 7am,
1pm, and 9pm. Follows is the list of dates and hours when the
"Permission denied" errors showed up. They match up to a tee (although
the error apparently sometime
Apparently we got lucky on all four servers with the latest cycle, so
nothing to report. Load (both reading and writing) is quite light today
so perhaps the bug is only triggered under a higher load. It seems the
problem typically doesn't show up on weekends either (when load is also
much lighter
The error messages refer to the old relfilenode (in 3 out of 3
occurrences today).
Pete
>>> Tom Lane <[EMAIL PROTECTED]> 04/14/06 2:41 am >>>
OK ... but what's still unclear is whether the failures are occurring
against the old relfilenode (the one just removed by the CLUSTER) or
the
new one just
Hi all,
In the last couple of days, we've been bitten (a couple of times, on
different servers) by an apparent glitch or bad interaction in the
Windows implementation of rename().
The relevant log message is:
[2006-04-17 16:49:22.583 ] 2252 LOG: could not rename file
"pg_xlog/0001010A00
Unfortunately, it's not that simple. It would be straightforward to
track down if it were.
In response to other questions:
It's Postgres 8.1.3 running on Windows 2003 Server. No anti-virus
software is installed. The servers are essentially bare except for the
OS and Postgres.
We have "handle
They are local.
Pete
>>> "Harald Armin Massa" <[EMAIL PROTECTED]> 04/18/06 4:35 pm
>>>
"G" - is that really a LOKAL drive at that server, or rather some NAS
or similiar?
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will igno
It's definitely possible. Both failures occurred around the end of the
business day as update traffic would have been coasting to a stop. The
middle tier never closes a connection unless it's forced to (e.g. as a
result of a query error, connection going away, etc.)
Pete
>>> Tom Lane <[EMAIL
Does that also explain why an attempt to make a new connection just
hangs?
One other thing regarding that is that connection attempt seems to
kinda, sorta succeed. It never makes it as far as a command prompt, but
on the "stop -m immediate", psql does print the "HINT: In a moment you
should be a
601 - 700 of 900 matches
Mail list logo
