The following bug has been logged on the website:
Bug reference: 6646
Logged by: Steven Huwig
Email address: st...@empiricalthought.com
PostgreSQL version: 9.1.3
Operating system: Linux
Description:
I am trying to raise standard SQL errors from inside PL/Python code.
The following bug has been logged online:
Bug reference: 6203
Logged by: Steve
Email address: argon...@yandex.ru
PostgreSQL version: 9.1.0
Operating system: Windows XP SP3 x32
Description:Building libpq with Visual Studio 9.0 error
Details:
When I'm trying to
The following bug has been logged online:
Bug reference: 6140
Logged by: Steve Boyd
Email address: sboy...@yahoo.com
PostgreSQL version: 8.3.12
Operating system: Windows Server 2003 R2 SP2
Description:PostgreSQL Server Service Not Starting
Details:
Good morning
The following bug has been logged online:
Bug reference: 6083
Logged by: Steve Haslam
Email address: araq...@googlemail.com
PostgreSQL version: 9.0.4
Operating system: Debian GNU/Linux (amd64)
Description:psql script line numbers incorrectly count \copy data
Details
The following bug has been logged online:
Bug reference: 6082
Logged by: Steve Haslam
Email address: araq...@googlemail.com
PostgreSQL version: 9.0.4
Operating system: Debian GNU/Linux (amd64)
Description:server segfault - pg_stat_reset_shared(null)
Details
normal |
volatile | cepheids | plpythonu | :yadda |
====
Please explain.
--
| - - - - - - - - - - - - - - - - - - - - - - - - -
| Steve White +49(331)7499-202
| E-ScienceZi. 27 Villa Turb
Hi Tom,
I already agreed to Kevin's proposed syntax, and it is better than
my suggestion, but mine isn't quite as crazy as you make out.
On 1.02.11, Tom Lane wrote:
> Steve White writes:
> > Try this instead:
>
> > ==
UNCTION yadda_yadda() returns text language plpythonu as
> > \iq yadda_yadda.py
> > ;
Yes this will work for me.
>
> Just got this --- looks like we independently arrived at the same
> conclusion.
>
> regards, tom lane
>
--
| - - - - -
Hi again,
Now that I know what got you all riled, I can propose something that
might be more satisfactory. See below.
On 1.02.11, Steve White wrote:
> Hi again, all,
>
> OK I think I now know what the misunderstanding is.
>
> > [Please don't top-post.
Hi again, all,
OK I think I now know what the misunderstanding is.
> [Please don't top-post. Rearranged for clarity.]
>
> Steve White wrote:
> > On 1.02.11, Tom Lane wrote:
> >> Steve White writes:
> >>> It would be really nice to have a way to load
Hi Kevin,
On 1.02.11, Kevin Grittner wrote:
> [Please don't top-post. Rearranged for clarity.]
>
As you like.
> Steve White wrote:
> > On 1.02.11, Tom Lane wrote:
> >> Steve White writes:
> >>> It would be really nice to have a way to load script
Hi Pavel,
On 1.02.11, Pavel Stehule wrote:
> Hello
>
> 2011/2/1 Steve White :
> > Hi Tom,
> >
> > This seems like a detail that is beside the point I'm making.
> > But security is important, so let's think about it.
> >
> > PostgreSQL ha
ing anything stupid that would open a security hole."
Cheers again!
On 1.02.11, Tom Lane wrote:
> Steve White writes:
> > It would be really nice to have a way to load script (especially Python
> > and Perl) from a separate file into a function body.
>
> This seem
!
--
| - - - - - - - - - - - - - - - - - - - - - - - - -
| Steve White +49(331)7499-202
| E-ScienceZi. 27 Villa Turbulenz
| - - - - - - - - - - - - - - - - - - - - - - - - -
| Astrophysikalisches Institut Potsdam (AIP)
| An der
perhaps
with an environment variable replacement (e.g. $LIBDIR).
Cheers!
--
| - - - - - - - - - - - - - - - - - - - - - - - - -
| Steve White +49(331)7499-202
| E-ScienceZi. 27
On Aug 1, 2010, at 10:11 PM, Tom Lane wrote:
> "Steve Atkins" writes:
>> I have a database that contains two tables (partminer and partminer2), and
>> two sequences (partminer2_id_seq and partminer_pk), on a 9.0beta3
>> installation built from source with default
The following bug has been logged online:
Bug reference: 5589
Logged by: Steve Atkins
Email address: st...@blighty.com
PostgreSQL version: 9.0beta3
Operating system: OS X
Description:psql dies with bad free() in libedit
Details:
I have a database that contains two
The following bug has been logged online:
Bug reference: 5397
Logged by: Steve White
Email address: stevan_wh...@hotmail.com
PostgreSQL version: 8.4.2
Operating system: Ubuntu 10.5 beta
Description:powertop reports excessive wakeups
Details:
This is a Samsung NC20
===
Cheers!
--
| - - - - - - - - - - - - - - - - - - - - - - - - -
| Steve White +49(331)7499-202
| e-Science / AstroGrid-D Zi. 35 Bg. 20
| - - - - - - - - - - - - - - - - - - - - - - - - -
| Astrophysikalisches Institut Potsdam (A
ing in the PL/Perl section.
Specifically, a user might want to know if it is actually dangerous to
use PL/Python, etc. If it is dangerous, how, and for whom? Where should
one be careful?
Cheers!
On 11.01.10, Robert Haas wrote:
> On Mon, Jan 11, 2010 at 11:41 AM, Steve White wrote:
> > I
The following bug has been logged online:
Bug reference: 5272
Logged by: Steve White
Email address: swh...@aip.de
PostgreSQL version: 8.4.2
Operating system: Linux
Description:PL/Python SELECT: return composite fields as dict, not
str
Details:
Hi,
As recently
because of the size of this sample when compared to the overall data set (in
fact the production servers have it set to 700 and it makes little
real-world difference), so we'll go with your initial suggestion and upgrade
to 8.4. Thanks again; this has been an good set of lessons to learn.
Steve
>Steve McLellan writes:
>> Thanks! Installing 8.4 and setting cursor_tuple_fraction to 1.0 does seem
to
>> force it to execute in the same time as not using the cursor, and we'll
>> probably go with this solution (the only reason we're using cursors is to
>&
n the explain
- the DECLARE syntax doesn't seem to allow it. Do I need to do it through
plpgsql?
Thanks again,
Steve McLellan
> On Thu, Jul 16, 2009 at 12:34 PM, Steve Caligo
> wrote:
>> 2) FIRST TRY, USING "UPDATE WHERE ID = ( SELECT )"
>> The goal is to have two clients set their unique ID to a
>> single/different
>> row from the table. First, using "limit" in a sli
The following bug has been logged online:
Bug reference: 4925
Logged by: Steve Caligo
Email address: steve.cal...@ctie.etat.lu
PostgreSQL version: 8.3.7 and 8.4.0
Operating system: Archlinux and Gentoo 8.3.7, Gentoo 8.4.0
Description:"select ... for update&quo
Terrific, thanks for that. I'd figured out the first trick you
suggested, but the second is much clearer.
-Steve
On 6 Jul 2009, at 12:28, Dimitri Fontaine wrote:
Steve Purcell writes:
# su - postgres -c "env PGCLUSTER=8.3/main pg_dump openx|env
PGCLUSTER=8.4/main pg_
-C"
And the debian pg_wrapper script ends up selecting the 8.3 pg_dump
binary in the first case. I'll have to figure out if there's even a
way to execute the newer pg_dump against the old database, which I
expect to be fiddly.
Thanks again, and sorry for the noise.
-Steve
The following bug has been logged online:
Bug reference: 4901
Logged by: Steve Purcell
Email address: st...@sanityinc.com
PostgreSQL version: 8.4.0
Operating system: Linux (Debian Unstable)
Description:Column name "window" breaks pg_dump/pg_restore
Details
Try setting the variable lc_collate, either in an individual session
using SET or (to change it for all session) in postgresql.conf.
Craig Ringer wrote:
CK Leung wrote:
I create a new database use UTF-8 and SQL_ASCII, same result found, how
can i fix this problem ?
If
What's the timing of the errors? Is there a chance that we are sending
the kill signal before the signal handling thread has actually started
*and created the named pipe*?
We set up the signal handling stuff pretty early, but we do seem to let
the postmaster continue it's work before it's up...
Bruce Momjian wrote:
Uh, no file attachment.
I attached the patch file to my Feb 3 post, but I'll attach it again.
---
Marshall, Steve wrote:
Any thoughts on whether or not this patch shou
iding transient
pseudo-failures.
A patch with this change is attached. It should be applied to the
8.3.5 version of src/port/kill.c
Steve
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
s the worst case found in a fairly long
stress test. This strikes me as a reasonable balance between failing
quickly in truly erroneous cases, while still avoiding transient
pseudo-failures.
A patch with this change is attached. It should be applied to the
8.3.5 version of src/port/kill.c
has ideas on what else should be tested,
please let me know.
Steve
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ions. In that case, we would need to
ensure ERROR_GEN_FAILURE is translated to an appropriate errno value.
I think detecting whether or not the listener backend exists is really
the check we want. However, there may be performance considerations to
different ways of checking this.
Any thought
uot;). I'm open to ideas on how to dig further.
Steve
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Wednesday, January 28, 2009 12:44 PM
To: Marshall, Steve
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] pg_listener entries deleted under heavy NOTIFY load
onl
errno value of ESRCH.
The Windows error is a bit surprising, at least to me -- I expected
something indicating the pipe was full. Does anyone have a richer
interpretation of this error?
Thanks,
Steve
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Alvaro Herrera writes
Marshall, Steve wrote:
Any thoughts on how to confirm or deny Theory A?
Alvaro Herrera wrote:
Try changing the 1000 to NMPWAIT_WAIT_FOREVER
I'd tried Alvaro suggestion and it fixed the problem in my test case.
With the original code, the test would consist
Tome Lane wrote:
Theory B is that you've got some broken antivirus code on there that is
arbitrarily interfering with the pipe access. The lack of any similar
previous reports suggests that there's some local issue contributing ,,,
Steve Marshall wrote:
To explore Theory B, I'll
"Marshall, Steve" writes:
> Under a heavy load of NOTIFY events, entries in the pg_listener table
> for some events are deleted, effectively acting as though UNLISTEN
> were called.
> I have only been able to make this occur on a PostgreSQL server
> running on
Under a heavy load of NOTIFY events, entries in the pg_listener table
for some events are deleted, effectively acting as though UNLISTEN were
called.
I have only been able to make this occur on a PostgreSQL server running
on Windows. I cannot reproduce under Linux.
PostgreSQL version: 8.3.4
The following bug has been logged online:
Bug reference: 4440
Logged by: Steve Jones
Email address: [EMAIL PROTECTED]
PostgreSQL version: V8.1.4
Operating system: Windows XP + sp3
Description:positioned_load in pos_newload failed
Details:
I have an issue using the
Hal Black wrote:
The following bug has been logged online:
Bug reference: 4435
Logged by: Hal Black
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Ubuntu Hardy 8.04.1 LTS
Description:pg_ctl start doesn't detach when run via SSH
Details:
PostgreSQL 8.3 added a new optimization to avoid sorting in queries that
use ORDER BY ... LIMIT. This optimization does not work when the query
is issued to a parent table with several children, such as a partitioned
table.
PostgreSQL version: 8.3.1
Operating System:RedHat Enterprise Li
The following bug has been logged online:
Bug reference: 4049
Logged by: Steve Clark
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: FreeBSD 6.2 patch level 7
Description:ecpg library causes signal 11 when
--enable-thread-safety is turned
Tom Lane wrote:
"Steve Clark" <[EMAIL PROTECTED]> writes:
Until 8.3.0 the following worked:
SELECT coalesce(param_value,chr(0)) from t_system_params where param_name =
'default_unit_key';
It would have "worked" only for rather small values of "work&
The following bug has been logged online:
Bug reference: 4007
Logged by: Steve Clark
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: FreeBSD 6.2
Description:chr(0) doesn't work anymore
Details:
Until 8.3.0 the following worked:
S
7;t work in 8.3 anymore. You need to cast before calling the
function, ie, func(col::inet).
...
However, this doesn't explain why ecpg fails to generate valid C code.
Michael
Hi Michael,
The patch fixed the compile errors.
Thanks,
Steve
--
Sent via pgsql-bugs mailing list (pgsql-bugs@pos
u.element->lineno);
if (ind_type != NULL)
{
Thank Michael,
I'll give it a try.
Steve
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your Subscription:
http://mail.postgresql.org/mj/mj_wwwusr?domain=postgresql.org&extra=pgsql-bugs
The following bug has been logged online:
Bug reference: 4001
Logged by: Stephen Clark
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: FreeBSD 6.2
Description:ecpg produces code that won't compile
Details:
Below is a code fragment that co
-switch dependent; these
> look to be the switches Martin tested with.
So strangely, when I first ran this test case I recall being able to
reproduce the SIGFPE; but now going back to it I'm getting the correct
"division by zero" output.
But postgresql still fails to build wit
On Wed, Nov 07, 2007 at 01:49:53PM -0500, Tom Lane wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > It may be specific to particular versions of glibc and the kernel. At least
> > one of the test regressions is actually due to the bug described in
> > <http:/
00014.html>; I haven't dug
into the rest of the failures further at this point.
But if it can be reproduced on other distros as well, all the better.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I c
ite a while; it
was added in in the TCL 8.2 release, circa 2000.
We hope this patch will be considered for a future PostgreSQL release.
Steve Marshall
Paul Bayer
Doug Knight
WSI Corporation
pltcl_multithread_bug_test.tar.gz
Description: pltcl_multithread_bug_test.tar.gz
*** pltcl.c.orig
ected
several versions of Pg-DBD, up to version 1.49. It should be fixed in
later versions of Pg-DBD.
The fix is a one line change; a patch file is attached.
I hope this is helpful,
Steve Marshall
*** dbdimp.c.1.49 2006-08-29 16:04:37.0 -0400
--- dbdimp.c2006-08-29 16:23:32.
The following bug has been logged online:
Bug reference: 3181
Logged by: Steve Gieseking
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Linux Fedora Core 6
Description:ecpg generating wrong code
Details:
I am maintaining code that uses
of Pg too. At
least I think it's a bug.
Let me know if you can't replicate and I'll happily work with someone
to get it to happen. I could make it stop happening until I tried not
installing those three options.
Best regards and thanks for a wonderful product,
Steve
p.s. I tried
The following bug has been logged online:
Bug reference: 2856
Logged by: Steve Langridge
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows XP Pro SP2
Description:Jdbc 4 connector running on JDK 1.6 should not raise
exception for
No ideas on this I take it?
>
> The following bug has been logged online:
>
> Bug reference: 2525
> Logged by: Steve McWilliams
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.4
> Operating system: Windows 2000
> Description:
The following bug has been logged online:
Bug reference: 2525
Logged by: Steve McWilliams
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Windows 2000
Description:"No buffer space available" error running pg_dump on
win2k for l
Any known way to log at the JDBC level? When I get a little time I'm
going to write a test that bypasses Eclipse and SQLExplorer.
On Wed, 5 Oct 2005, Oliver Jowett wrote:
> Alvaro Herrera wrote:
> > On Fri, Sep 30, 2005 at 10:37:05PM -0500, Steve Peterson wrote:
> >
> &
10:04:04PM -0500, Steve Peterson wrote:
> Is this a bug or some artifact of the SQL language that I've never
> seen before?
>
> SELECT v_id
> FROM table
> WHERE col = 'V')
> AND blah
>
> executes without errors, ignoring the closing paren and everything
>
Is this a bug or some artifact of the SQL language that I've never
seen before?
SELECT v_id
FROM table
WHERE col = 'V')
AND blah
executes without errors, ignoring the closing paren and everything thereafter.
Platform: PostgreSQL 8.0.3 on Intel / Windows XP
---(end of
On 2005-08-26 16:17, "Tom Lane" <[EMAIL PROTECTED]> wrote:
> "Steve Wormley" <[EMAIL PROTECTED]> writes:
>> Did a dump and restore of my DB to 8.1beta1 (running concurrently with
>> 8.0.3) and performance on the same query is about 50% slower with t
The following bug has been logged online:
Bug reference: 1851
Logged by: Steve Wormley
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1beta1
Operating system: RedHat Linux, Kernel: 2.6.12.2
Description:Performance reduction from 8.0.3
Details:
Did a dump
At 09:47 AM 8/11/2005, Richard Huxton wrote:
Steve Peterson wrote:
Running COPY FROM on a Windows server; using a Windows-format fully
qualified path with backslashes results in the backslashes being interpreted
as escapes.
Did you escape the backslashes: C:\\Windows\\Path ?
Nope. I used a
The following bug has been logged online:
Bug reference: 1819
Logged by: Steve Peterson
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Windows XP SP 2
Description:COPY filename rejects Windows format path
Details:
Running COPY FROM on
x27;epoch\'
+ interval \'1 second\' * $1;'
language sql immutable;
Is there a better way?
Steve.
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command
The following bug has been logged online:
Bug reference: 1757
Logged by: Steve Bennett
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.3
Operating system: Linux
Description:timestamp 'epoch' is not absolute
Details:
I'm seeing a rather a
The following bug has been logged online:
Bug reference: 1716
Logged by: steve owen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.8
Operating system: RHEL4
Description:FATAL: XX000: failed to initialize lc_messages to ""
Details:
I found this
however.
Any suggestions? Thanks in advance.
Steve McWilliams
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
The following bug has been logged online:
Bug reference: 1394
Logged by: Steve Nicolai
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.6
Operating system: Fedora Core 2
Description:LIKE doesn't seem to use an index
Details:
I've inherited som
e C.
>
> creating directory C:/E-NetAware-Data/db ... initdb: failed
>
> The exit code returned by initdb is "1". Any ideas why this would be
> failing? I didn't see any similar report about this in the mailing list
> archives. My next step is to recompile initd
a/db ... initdb: failed
The exit code returned by initdb is "1". Any ideas why this would be
failing? I didn't see any similar report about this in the mailing list
archives. My next step is to recompile initdb.exe and put in more
temporary debug print statements and have the customer r
gestions? For a temporary work around I have hacked my pg_ctl.c to
wait 5 seconds before declaring the service to be in the running state.
Thanks in advance.
Steve McWilliams
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
on to wait
for it to start.
Thanks,
Steve McWilliams
---(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
ay of specifying a log file for postmaster output when
running pg_ctl.exe as a service? The "-l" option does not seem to work.
Thanks in advance.
Steve McWilliams
---(end of broadcast)---
TIP 2: you can get off all lists at once with
ruly able to accept clients.
Any suggestions? Thanks in advance.
Steve McWilliams
---(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
d in as while
> attempting to install the service, is it an admin account that has the
> required privileges?
>
> Steve McWilliams wrote:
>
>>I am unable to run pg_autovacuum as a windows service. I am using
>> 8.0.0beta4 on Windows XP Pro. When I execute the follow
on the same machine.
Note that if I instead run pg_autovacuum from the command line, not as a
service, then it works fine:
pg_autovacuum.exe -U db_user -p 15432 -L my_log
Any ideas? Thanks in advance.
Steve McWilliams
---(end of broadcast
og" option passed in would get ignored, according to pg-ctl.c.
Is there some other way that we should be configuring a log file when
running pg_ctl as a service on windows?
Thanks.
Steve McWilliams
Software Engineer
Emprisa Networks
703-691-0433x21
[EMAIL PROTECTED]
The information contained
> "Steve McWilliams" <[EMAIL PROTECTED]> writes:
>> I am just starting to test out Postgres8 beta1 and notice that the
>> deadlock detection mechanism is not working (under windows XP pro with
>> service pack 1). I am using the version of Postgres built by
I
have not tried this using a version of 8beta1 built using cygwin, but I
have run versin 7.4 under cygwin before without this problem.
I tried uncommenting the deadlock.tx.timeout=1000 value in
postgresql.conf, just in case this wasn't already the default value, but
it didn't seem to hel
On Friday 27 August 2004 20:21, Tom Lane wrote:
> Steve Ingram <[EMAIL PROTECTED]> writes:
> > When I pg_dump out the database, it outputs all the tables, functions,
> > types as you'd expect, but it outputs table definitions that reference
> > postgis functions/ty
I'm just blind :) )
I'm guessing the info is just coming out in OID order?
Of course, it may be an impossible task to do anything about this
and in my case I do have workarounds (not to mention I can edit the
file :) ), but I thought I'd mention it anyway.
Wonderful datab
On Wed, Mar 03, 2004 at 06:27:07PM -0500, Tom Lane wrote:
> Steve Atkins <[EMAIL PROTECTED]> writes:
> >> test=> select -2147483648::int;
> >> ERROR: integer out of range
>
> There is no bug here. You are mistakenly assuming that the above
> represents
&
for
> it except perhaps check for INT_MIN int he int84 function, but I ran
> some tests and that didn't work either.
I don't read it that way. INT_MIN is correctly read as a signed int,
but it can't be defined as -0x800 as that would be parsed as
-(0x8000) and the constant 0x8000 is unsigned.
Cheers,
Steve
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
y after an initdb.
I see the same bug on Solaris, built with Forte C in 64 bit mode.
Cheers,
Steve
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
reindexing the entire database several times.
Please let me know if there is a fix to this.
Thanks.
Steve Thames
Softlife Consulting, Inc.
530-672-6908
www.softlife.com
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
the data column
>
> '¤' means '¤', not anything else. Maybe you want to try '\244'
> (octal).
That was a literal character 164 that the browser seems to have munged when
uploading the form (the script is also available in raw form using the URI
at
RPM for PostgreSQL 7.1.3, the size is about 87K.
Thanks for the help.
Steve
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
You must patch postgresql in order to run it under cygwin + windows 2000.
The "filename_completion_function" is named
"rl_filename_completion_function" under cygwin.
That's why it's not found.
The patch will solve the problem and other memory allocation problems
appearing under windows 2000.
You
assume that the server and psql client versions match on a specific
machine.
Sorry again for my lack of diligence in the "bug" report.
-sp-
cc: [EMAIL PROTECTED]
Date: Thu, 06 Sep 2001 15:24:54 -0400
From: Tom Lane <[EMAIL PROTECTED]>
Steve Pothier <[EMAIL PRO
#x27;kill %p', psql
terminates and the backend continues copying records from line
841... and copies to the end. Subsequently (in a new psql session) I
can see all the records have been loaded properly.
Hope this helps.
Regards, Steve Woodcock
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
To Whom It May Concern:
Just wanted to share with you the errors I keep getting trying to upgrade my
current version 6.5 of Postgresql to 7.1.
1.) Installed 6.5 via the Red Hat linux install of 6.2
2.) Have plenty of hardware (dual 600's, 2Gig RAM, 18G HD).
3.) Downloaded 7.1 tar f
POSTGRESQL BUG REPORT TEMPLATE
Your name : Steve Woodcock
Your email address : [EMAIL PROTECTED
Do we know anybody with BSDI 4.1? LC_MESSAGES may have made it into that
release, though I have no way of checking this since my support contract has
expired :-(. I'll renew, but that doesn't help for an April release.
Regards,
- Steve
- Original Message -
From: Tom La
e happy to test
out any fixes.
Regards,
- Steve
- Original Message -
From: Tom Lane <[EMAIL PROTECTED]>
To: Steve Nunez <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Sunday, March 19, 2000 12:59 AM
Subject: Re: [BUGS] Where is a comp
Hello,
Note: There is no obvious bug
report form at http://www.postgresql.org.
POSTGRESQL BUG REPORT
TEMPLATE
100 matches
Mail list logo
