;t seem to work on Vista. MS think that
Process monitor is a replacement, but it lacks all the handy detailed
process introspection, thread control, etc that Process Explorer has.
Frustrating.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make chang
Dave Page wrote:
On Fri, Jun 27, 2008 at 6:26 PM, Craig Ringer
<[EMAIL PROTECTED]> wrote:
Alas, Process Explorer doesn't seem to work on Vista. MS think that Process
monitor is a replacement, but it lacks all the handy detailed process
introspection, thread control, etc that Proce
Craig Ringer wrote:
Dave Page wrote:
On Fri, Jun 27, 2008 at 6:26 PM, Craig Ringer
<[EMAIL PROTECTED]> wrote:
Alas, Process Explorer doesn't seem to work on Vista. MS think that
Process
monitor is a replacement, but it lacks all the handy detailed process
introspection, thread c
t was the previous database version?
- Can you provide DDL for the table?
- What is the exact data type of the field `somedate' ?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ock error 10004 »
It happens frequently, without using SSL (I have seen some post relative to
SSL with windows).
Any idea ?
The usual question with weird Windows errors: Do you have a virus
scanner? If so, have you tried completely disabling it or uninstalling
it (NOT just excluding Postgre
QL log) and the schema definition of the problem table as
obtained with psql's \d command.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
on a glibc system (essentially all Linux, at least) try using
LD_DEBUG to trace the linker's operation, too, and see if that tells you
anything useful:
LD_DEBUG="libs,files" su -l postgres ""
See this page for a simple summary:
http://www.wlug.org.nz/LD_DEBUG
It looks
irewall? If so, is it configured to permit the
stack builder to access the Internet?
Are you behind a proxy server that might limit access to some files?
Did you do a tcpdump or use wireshark to record the network
communication between client and server? If not, consider doing so.
--
Craig Ring
you STILL cannot find the answer and the question is about PostgreSQL
and Java/JDBC, consider posting a question on the PostgreSQL JDBC
mailing list.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
7; schema.
So: the user's report is incorrect in blaming pg_restore, but correct in
that comments on the public schema (and presumably other default schema)
aren't preserved by pg_dump | pg_restore. The real reason appears to be
that they're not dumped in the first place.
I
table.
Read the PostgreSQL JDBC documentation to find out how to use it. If you
still need help, consider posting on the JDBC list, but do make sure to
read the manual first.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ou're trying to do, what you've tried, and what went
wrong. Specify your operating system (eg "Ubuntu 8.04") and PostgreSQL
version (eg "8.3.1") as well as how you installed postgresql, and
anything else that you can see might be relevant.
--
Craig Ringer
--
uld continue to be accepted.
> /24 : IP must ends with .0
> /16 : IP must ends with .0.0
If you're going to do that, you might as well enforce it for any CIDR
subnet and say that the address given must be the network address, not a
host address within the network. That way it works for no
27;s another issue).
Arguably no SQL database should be described as "relational" - but in
practice, SQL describes a good and workable approximation of relational
theory that works in the real world and is useful to describe as
"relational" to distinguish it from other, co
or.
So ... in short, I see malloc() and free() as rather low level, and not
something I want to see at all in the significant parts of any
nontrivial program.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ay more work than would be worthwhile when you can just run
Pg on a modern machine and talk to it over the network.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
newer database servers.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Zahid Khan wrote:
>
>
> I am using 8.3.1 driver ,Is this changed in any new version ?
Not as far as I know. There might be problems if you were using, say, an
8.2.x driver with an 8.3 server, though.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org
,
compileable test case (example program) that can demonstrate this? Your
description doesn't exclude the possibility of leaks occurring as a
consequence of failure to free resources in the program using libpq.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make ch
) being operated on by the query that should work too.
Consider making a copy of your database and your log files before you
REINDEX in case one of the developers thinks it might actually be caused
by a PostgreSQL bug and wants to have a look.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list
hard poweroffs?
(Not that it should matter, but): Have you hard killed any backends
(kill -9 / SIGKILL)?
If you run a RAID verify using tw_cli or through the 3dm web interface,
does it report any block mismatches in the array?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ause CMake configuration didn't work properly. CMake
shouldn't have even generated a Makefile; the fact that it did suggests
that the error handling in the gammu cmake code is far from ideal.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
what happens.
Mention your Pg version and other things people need to know. It's also
likely to help if you punctuate your question so that people can follow
what you are saying; I found your writing very difficult to understand.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pg
IT. A good place to upload such files is http://rafb.net/ .
Alternately, if you're not comfortable building from source just install
PostgreSQL from the Ubuntu repositories (using backports if needed).
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.or
ation/scrubbing run too.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
e to your desktop (right click, "Save Link As...") and
opening the downloaded PDF directly from Adobe Reader, rather than via
your web browser.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
u are attempting to download is
- WHAT THE FULL, EXACT TEXT OF THE ERROR MESSAGE YOU GET IS
- What PDF reader you have installed
- Whether that has a browser plugin active or not
- Whether you're trying to download the PDF (right click -> save as)
or read it embedded in the browser
--
Craig Ri
un:
sudo apt-get build-dep postgresql
In most cases Ubuntu builds the most complete and generic configuration
of the app so that'll get you what you need.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www
your file
systems OK ?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
meblock->blockdata[11];
Static analysis tools won't realise what's going on, and will complain.
I'd say after a quick glance that that's what's happening here, though
I'm far from certain.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql
uding things like your operating system
and the version of your operating system.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
e rather than upgrading gcc and binutils you might be able to modify
the configure script and/or makefile to work around it. I wouldn't be
too sure how; I'd need to dig into what was happening and probably have
an old box on hand.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
see below). Does
> anyone know what the cause might be? Or better still, how to fix it? :)
What is "cc" in this context?
cc -v
> cc -c -I/usr/local/PostgreSQL/include -I/usr/local/include
Is it possible that you have old or conflicting PostgreSQL headers in
/usr/local/includ
bases, re-initdb with the new collation settings, and
re-load your databases.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Have you checked the Event Viewer to see if there are any errors
starting PostgreSQL? (Control Panel -> Administrative Tools -> Event
Viewer on WinXP).
Have you looked at the PostgreSQL log files to see what, if anything,
went wrong starting up?
--
Craig Ringer
--
Sent via pgsq
ory. That won't work.
Specify a subdirectory of the install directory if you must have it in
there.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
software be uninstalled, not just disabled or
told to ignore PostgreSQL.
Well-designed, bug-free antivirus software shouldn't affect PostgreSQL,
but there doesn't seem to be much of that around.
In any case, you shouldn't really need antivirus software on a database
server.
--
Craig Ringe
log/postgresql or something like that - it depends on exactly
how the distro packaged PostgreSQL.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
eSQL instance
with a fresh database had issues, but that's probably not practical for
you to test.
Most likely it's some kind of corrupt database triggering a subtle bug
somewhere in Pg, anyway...
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To mak
inform the server that the client will be sending differently
encoded data.
In other words, you can't use 'SET client_encoding' to change what
encoding the client uses, only how the server interprets the bytes it
gets from the client.
--
Craig Ringer
--
Sent via pgsql-bugs mailing
correctly.
>
> AFAICS this just depends on "pidof postmaster". Perhaps you should be
> filing a bug against pidof.
First, though, make sure that SELinux isn't hiding the `postmaster'
process from your normal users. Make sure you can actually see it with
`ps aux
ng to mailing lists.
On Windows, it might be nice to be able to set a language for Pg.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
hat means that the terminal will
send 0xe2 0x80 0xb0 for per-mille, which when interpreted as win1250
becomes ‰ , so that's what the server thinks you sent it.
In that case, though, you'd find that the euro symbol, which isn't
defined in latin-2, will cause an error:
ER
it _does_ finish ... eventually. It might be doing
something that scales very poorly with number of input rows, like a
nested loop within a nested loop.
Can you provide EXPLAIN ANALYZE output for the problem query?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
T
ed yet.
Not in previous versions.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
aries.
You may need to install debuginfo RPMs for PostgreSQL and glibc at the
very least, then repeat the process of collecting backtrace information.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
header files.
If you're really stuck with build scripts or tools you can't change, you
can always create an NTFS junction point (like a symbolic link) to remap
the include dir somewhere else.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
faces. People seem to lose passwords a _lot_ .
Some info in the docs on changing/deleting the Pg service account might
also not be a bad idea.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
contents so nobody can see
what might be wrong with it. The config file is the file whose location
is given in the error message you saw.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ftware for
in-depth assistance.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
y, so
I never have to touch the actual win32 bits and know very little about
things like win32's threading. As such, if I try converting it myself I
won't be confident I'm really accurately testing the same thing you are).
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql
On 23/08/2009 10:37 AM, Craig Ringer wrote:
On 19/08/2009 11:50 PM, Shivesh Wangrungvichaisri wrote:
Logged by: Shivesh Wangrungvichaisri
Email address: s...@appsig.com
PostgreSQL version: 8.3.7
Operating system: Windows XP x64 / Windows 7 x64
Description: postgres.exe memory consumption keeps
another, etc, so I'm not sure where it's going yet. Valgrind
doesn't support Windows and all the Windows leak-checking tools cost
$LOTS so I can't just hook it up to a heap analyzer / leak checker. Sigh.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresq
.
Auto Screen Recorder from:
http://wisdom-soft.com/products/screenhunter_free.htm
might be handy for that, by the way.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 23/08/2009 12:42 PM, Greg Stark wrote:
On Sun, Aug 23, 2009 at 4:48 AM, Craig
Ringer wrote:
Interestingly, though, the test program does appear to be leaking - at
least, the peak working set slowly climbs. It's all private working set. Not
sure why yet since the memory use looks li
ee
the problem please follow up here, or try the patch for the issuye
proposed on the pgsql-general list.
> In these cases their .NET app returns this error
> Exception of type 'System.OutOfMemoryException' was thrown
That's probably a bug in their application caused by failure to
(or just use an implicit autocommit transaction) but if you do anything
more complex in your transactions you risk deadlocks between concurrent
transactions, awful performance, huge commit delays, and more.
Search the pgsql-general mailing list archives for "gapless sequence"
for mo
ny signs of anything odd going on, but right now it looks
sensible.
SandBox.exe is growing in the same way my locally built test program is.
Weird. I think I'm going to have to recompile PostgreSQL's libpq using
VC++8 in memory debugging mode. Sigh.
--
Craig Ringer
--
Sent via pgsql
monstrating the problem and we'll need different debugging tactics
instead.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
PostgreSQL (or at least libpq)
from sources using VC++8 in debug mode with memory tracing enabled.
I'll also try building it on a Linux machine to see if it's a
Windows-specific issue.
Thanks for your persistence on this. I'll follow up in a bit when I've
learned more about what
t's very program specific - it's part of the program's command line
parsing and argument processing, not cmd.exe / CreateProcess(...)'s
handling of the command line arguments.
Most Windows utilities, including command-line tools, handle
forward-slash paths quite fine. It'
d
that the growth of the test program was libpq working as designed.
It looks like we're done here.
--
Craig Ringer
// Standard C++ headers
#include
#include
#include
// PostgreSQL libpq headers
#include "libpq-fe.h"
#include "libpq/libpq-fs.h"
// Intel TBB header for thre
issues.
If it's a really rare and quirky hard to trigger bug, where do you even
start looking without *some* idea what happened to trigger the issue? Do
you have any idea what might've started it in your case?
*** DID YOU TAKE COPIES OF YOUR DATA FILES BEFORE "FIXING" THEM **
7;s `md' software RAID, which while
imperfect seems to be pretty sane in terms of data preservation.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
iven incident could be a rarely triggered Pg bug (ie: Pg writes wrong
data, writes garbage to files, etc) or whether it's something external
like hardware or interfering 3rd party software.
Make sense?
--
Craig Ringer
* For example, WD Caviar disks a few years ago used to spin down without
req
to provide an explanation of where the problem
you are reporting arises, what actually happens, what you expect to
happen instead, and what exactly you change to "fix" it.
It might help to turn detailed error logging on in the server and
capture the server error log for your &q
t but didn't found.
Build and install PostgreSQL 8.2 from source.
This is not a bug.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
황수진 wrote:
>
> postgres=# \encoding
> EUC_KR
> postgres=# CREATE DATABASE 수진이_친구;
> WARNING: could not determine encoding for locale "Korean_Korea.949": codeset
> is
> "CP949"
> 상세정보: Please report this to http://www.postgresql.org/mailpref/pgsql-bugs
about locale handling on Windows.
--
Craig Ringer
Tom Lane wrote:
> "Kenaniah Cerny" writes:
>> Segfault party
>
> I couldn't reproduce a crash given this information.
Which probably means 'it's time to hook up `gdb' and get a backtrace of
the crash'.
--
Craig Ringer
--
Sent via pgsq
(exact URL please), the file size of the installer, the
MD5SUM of the installer (search the Internet for how to do this), the
EXACT error message, any Windows error log entries that appear in the
Event Viewer when you run the installer, etc.
--
Craig Ringer
t;program files" folder is visible in C:\ in Windows Explorer
it might still open; Windows virtualises some paths).
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
han:50,cmd
(Filter for just the postmaster and postgres processes if you want)
> Both filesystems are EXT-4.
That's interesting given the issues you're having...
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
;dmesg" command.
I won't be too surprised if you see a kernel stack trace for your httpd
process(es) starting something like this:
schedule+0x18/0x40
start_this_handle+0x374/0x508
jbd2_journal_start+0xbc/0x11c
ext4_journal_start_sb+0x5c/0x84
ext4_dirty_inode+0xd4/0xf0
--
C
ketcall+0x1b7/0x2b0
Oct 27 14:20:19 wallace kernel: [13668207.501781] [] ?
sys_gettimeofday+0x2b/0x70
Oct 27 14:20:19 wallace kernel: [13668207.501781] []
sysenter_do_call+0x12/0x2f
BTW, if you do get kernel task trace information and you decide to
redact it, it'd be good to include at le
d why tar doesn't detect the gzip and bzip2 file
headers and automatically shell out to the appropriate helper. Or just
link to zlib, for that matter. "purist" issues I expect.)
Anyway, if "file" says something else, post the result here along with
the result of:
od -x post
[] ? kmap_atomic_prot+0x1b0/0x1da
> [] ? ipc_lock+0x2b/0x45
> [] sys_semtimedop+0x4ca/0x579
> [] ? handle_mm_fault+0x2e8/0x6ec
> [] ? kunmap_atomic+0x87/0xa7
> [] ? do_page_fault+0x3ac/0x710
> [] ? resched_task+0x3a/0x6e
> [] ? _spin_unlock_irqrestore+0x22/0x38
> [
0KiB Write Merges:0,
> 0KiB
> Read depth: 0 Write depth: 0
> IO unplugs:53 Timer unplugs: 6
(ignore quotes; working around a stuipid Thunderbird limitation)
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
the machine, and it already has lots of them when it's installed.
> Baffled. I am blaming MS and VISTA at this point.
Incorrectly so in this case, I'm afraid.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
stgreSQL in. If you use PgAdmin III you can open postgresql.conf via
its menus - it's under "Tools" -> "Server Configuration".
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ls
you the line number and what's wrong with it. I can't actually fix it
for you, and you already have enough information to fix it yourself.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
he single-ROW result of the
subquery into a regular 4-tuple.
Is the co0nversion of the ROW into individual fields in the SELECT
clause done by some kind of macro-expansion in parsing/planning?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To mak
(SELECT ((SELECT ROW(1,1,1,1)::test)::test))
AS tmp;
test
---
(1,1,1,1)
(1 row)
... is fine,
craig=# SELECT (tmp.*).* FROM (SELECT ((SELECT
ROW(1,1,1,1)::test)::test)) AS tmp;
test
---
(1,1,1,1)
(1 row)
... is ... WTF? How is "(tmp.*).*" the same as "tmp.*&qu
Sorry for the multiple replies-to-self, but this seemed worth
specifically noting: the expansion also results in multiple calls to
tuple-returning functions, even functions marked VOLATILE. For example:
CREATE OR REPLACE FUNCTION expandtest(INTEGER) RETURNS test AS $$
DECLARE
rec test;
BEGIN
, as 8.5 understands hex escapes in bytea values.
I guess bytea is kind of ugly to use in a text-based protocol :-(
because the query string has to be valid text in the client_encoding, so
bytea values containing data not valid in the client encoding must be
escaped in the parsed query string. T
's going on, though.
It'd be helpful if you could provide a process monitor log (in native
process monitor format) of the installation process, since that might
shed some light.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
Log about PostgreSQL?
Is there anything of interest at the end of the most recent log file in
the "pg_log" subdirectory of the PostgreSQL data directory?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql
t valid in its context.
WSAEADDRNOTAVAIL
4. I believe ever since I upgraded, the pg_log logs have been empty.
There is nothing much interesting in the prior few logs (just info
messages about starting up and shutting down etc.)
Not even server startup messages? When is the most recent log entry
mail then.
Thanks for letting us know rather than just going quiet when the problem
was fixed. It's nice to know when things work out, and it helps others
who search for answers later.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to
. Both S1 and S2 are same
except "LIMIT 1 " is added to S2.
Please read this:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
then re-post your question to the pgsql-general mailing list, including
appropriate EXPLAIN ANALYZE output for both queries, etc.
--
Craig
which, IIRC, is the standard way to do it. I don't have a copy to
check against to be sure.
Personally, I like the fact that Pg errs on the side of caution here
rather than guessing what you want.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgres
helpful enough to just go back toward the
bottom of the stack and dump the first few hundred frames:
(gdb) set pagination off
(gdb) set logging file debuglog.txt
(gdb) set logging on
(gdb) bt -200
... then paste the result directly into this.
--
Craig Ringer
--
Sent via pgsql-bugs mailing l
portal=0x2ab68018, count=2147483647,
> isTopLevel=1 '\001', dest=0x28bc4420, altdest=0x28bc4420,
> completionTag=0xbfbfe7d4 "") at pquery.c:779
> #14195 0x0829155f in exec_execute_message (portal_name=0x28bc4018 "",
> max_rows=2147483647) at postgres.c:1928
> Recursion within PL/PgSQL?
er ... sorry for stating the belated and obvious. I was dropped from the
CC on the other branch of this thread so it wasn't hitting my INBOX and
didn't realise it'd carried on until I saw it in my Pg list folder.
--
Craig Ringer
--
Sent via pgsql
:frequent signal 11 segfaults
Details:
I got postgres segfaults several times a day.
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
nice to have ulimit values settable via
postgresql.conf so that you didn't have to faff about editing init
scripts, though.
( TODO item? )
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
th battery backup,
plus plenty of disks in RAID 10 and plenty of RAM will make more
difference than about anything else.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
would be one way to do what you're
talking about.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
install
random libraries there are almost certainly wrong, and are parroting
advice that used to apply back in the Windows 95/98 days before Windows
preferentially loaded libraries from the same directory as the application.
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgres
ttempt to
start PostgreSQL is made?
--
Craig Ringer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
1 - 100 of 453 matches
Mail list logo
