POSTGRESQL BUG REPORT TEMPLATE
Your name : Ryan Rawson
Your email address : [EMAIL
The following bug has been logged on the website:
Bug reference: 6370
Logged by: Ryan Culpepper
Email address: r...@cs.utah.edu
PostgreSQL version: Unsupported/Unknown
Operating system: not applicable
Description:
This is a documentation bug (or feature request), not
The following bug has been logged online:
Bug reference: 4446
Logged by: Ryan Wallace
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.4
Operating system: Windows XP SP2
Description:Full text search cannot start with an apostrophe
Details:
A tsquery cannot
Your name: Nicholas Jakobsen, Ryan Wallace
Your email address: nicholas.jakob...@telus.net, ryw...@gmail.com
System Configuration:
-
Architecture (example: Intel Pentium): Intel Core 2 Duo
Operating System (example: Linux 2.4.18): OS X 10.5 (Leopard)
PostgreSQL version
The following bug has been logged online:
Bug reference: 5121
Logged by: Ryan Douglas
Email address: rdoug...@arbinet.com
PostgreSQL version: 8.4.1
Operating system: Fedora 11
Description:Segmentation Fault when using pam w/ krb5
Details:
Whenever I use psql to
16 0x005b25dc in BackendInitialize ()
#17 0x005b2ebc in ServerLoop ()
#18 0x005b559c in PostmasterMain ()
#19 0x005617d0 in main ()
-Original Message-
From: Heikki Linnakangas [mailto:heikki.linnakan...@enterprisedb.com]
Sent: Thursday, October 15, 2009 5:23 PM
To
ke of completeness, I'll install 8.4.1 on another machine
which has all the deps met and try to reproduce the problem.
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Thursday, October 15, 2009 6:07 PM
To: Douglas, Ryan
Cc: pgsql-bugs@postgreSQL.org
Subject: Re: [BUGS]
lt
<@ 2009-10-15 23:39:20.546 EDT>LOCATION: LogChildExit,
postmaster.c:2725
<@ 2009-10-15 23:39:20.546 EDT>LOG: 0: terminating any other
active server processes
.
.
.
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Thursday, October 15, 2009 7:26 PM
e-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Friday, October 16, 2009 1:01 AM
To: Douglas, Ryan
Subject: Re: [BUGS] BUG #5121: Segmentation Fault when using pam w/ krb5
"Douglas, Ryan" writes:
> Ok... I compiled 8.2.14 and 8.3.8 with the same configure options.
They
> both se
B7D75778
<@ 2009-10-16 12:16:07.196 EDT>LOG: redo is not required
<@ 2009-10-16 12:16:07.223 EDT>LOG: database system is ready to accept
connections
<@ 2009-10-16 12:16:07.223 EDT>LOG: autovacuum launcher started
-Ryan
-Original Message-
From: Tom Lane [mailto:t...@sss
per, postmaster.c:2236
<@ 2009-10-16 12:33:33.644 EDT>DEBUG: 0: reaping dead processes
<@ 2009-10-16 12:33:33.644 EDT>LOCATION: reaper, postmaster.c:2236
<@ 2009-10-16 12:33:33.644 EDT>LOG: 0: all server processes
terminated; reinitializing
-Original Message--
010)
at postmaster.c:1040
#20 0x00588900 in main (argc=1, argv=0x20b9010) at main.c:188
(gdb) print num_msg
$1 = 0
(gdb) print msg[0]
$2 = (const struct pam_message *) 0x0
(gdb)
-Original Message-
From: Magnus Hagander [mailto:mag...@hagander.net]
Sent: Friday, October 16,
It works like champ... cool.. thanks.
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Friday, October 16, 2009 4:15 PM
To: Douglas, Ryan
Cc: Magnus Hagander; pgsql-bugs
Subject: Re: [BUGS] BUG #5121: Segmentation Fault when using pam w/ krb5
"Douglas, Ryan&quo
On Wed, 12 Apr 2000, Tom Lane wrote:
> "Kevin P. Neal" <[EMAIL PROTECTED]> wrote:
> >>>> Here are minimal patches to get 7.0 beta 3 limping along on NetBSD/alpha
> >>>> release 1.4.1.
>
> Has anyone compared these to Ryan Kirkpatrick&#x
Inserting text with an apostrophe fails. Updating a record after it's
initial creation works fine.
PGAccess version: 0.98.7 (as included with Mandrake 8.2).
file: pgaccess/lib/tables.tcl
fixed lines: 547-548...
546: lappend PgAcVar(mw,$wn,newrec_fields) "\"$fld\""
547: regsub -all {'} $fldva
ct.pgc"
> char * connection_name = "myconnection" ;
>
> #line 7 "connect.pgc"
> char * uname = "myuser" ;
>
> #line 8 "connect.pgc"
> char * password = "mypassword" ;
> /* exec sql end declare section */
> #
ou to
EXEC SQL CONNECT TO :target as :connection_name user :uname using :password;
and have the uname and password C variables get passed correctly to the
ECPGconnect fucntion after epgc processing.
On Tue, Aug 19, 2003 at 12:17:08PM -1000, Ryan Mooney wrote:
>
> Hello,
>
> I'm
On Wed, Jan 04, 2012 at 09:36:57PM -0500, Tom Lane wrote:
> "Ryan P. Kelly" writes:
> > The signal handler installed by setup_cancel_handler() will ignore
> > attempts to exit psql should a host be unreachable.
>
> Hm. That may be worth doing something about, but
the application should simply always try and validate that its
transactions have in fact failed, but that is not a feasible solution (for
many reasons). Thoughts?
-- Ryan Lowe
On Tue, Feb 28, 2012 at 2:42 PM, Tom Lane wrote:
> "Kevin Grittner" writes:
> > Tom Lane wrote:
&
ds, \d looks like:
Schema | Name | Type | Owner
+---+--+---
public | child | table| ryan
public | parent| table| new_owner
But I would expect that without specifying only, I would get:
Schema | Name |
hstore
--
"a"=>",b=>1"
[db]> select 'a=>, b=>1'::hstore;
ERROR: Syntax error near 'b' at position 5
LINE 2: select 'a=>, b=>1'::hstore;
In my mind, all of these should have been rejected as erroneous input.
To
> >
>
> Since this is removing a syntax error and not creating one, I'd say it
> should be safe to backpatch.
-Ryan Kelly
diff --git a/contrib/hstore/hstore_io.c b/contrib/hstore/hstore_io.c
index 0eb48cf..f03dcdc 100644
--- a/contrib/hstore/hstore_io.c
+++ b/contrib/h
On Fri, Apr 27, 2012 at 10:22:11AM -0400, Tom Lane wrote:
> Ryan Kelly writes:
> > As long as we make it consistent on both sides of the '=>' (and document
> > it, too), then I don't really care either way. Currently you have to use
> > quotes to get an emp
x27;s apparently easy to create one.
> >
> > I wrote a quick patch to do that, and with the patch the index build
> > finished - but it took hours. And the index was 10GB in size, where the
> > heap is just 12 MB, and searches using the index take ages. Do you have a
> >
older version? It
appears that the version of psql in 9.2 beta 2 does the correct thing,
look at src/bin/psql/describe.c line 142 or so.
>
> Regards. Philippe.
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
-Ryan Kelly
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
-Ryan
$ cat t.sql
create table foo (id serial primary key, name text);
insert into foo (name) values ('joe');
esql.org/docs/9.1/static/indexes.html
http://www.postgresql.org/docs/9.1/static/using-explain.html
>
> Thanks in advance,
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pg
o_idx2 ON foo (f1) WHERE id > 10;
>
> COMMENT ON INDEX foo_idx2 IS 'whatever';
>
> create table foo2 (like foo including all);
>
> rollback;
>
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your su
rashes.
>
> regards, tom lane
The latest on this patch can be found here:
http://archives.postgresql.org/message-id/500151c4.5010...@enterprisedb.com
-Ryan Kelly
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ndows 8
> Description:
>
> "pg_dump -Z1 my_db > backup" always make corrupted package.
What does this mean? How did you verify that you got a "corrupted
package"?
> When I try it on postgres database which created from installation: "pg_dump
> pos
ior is but I would think that 'last
> day of a month' + '1 month'::interval would give 'last day of next month'.
>
> I realize on January 29-30th I am not sure what the expected behavior should
> be.
>
'1 month'::interval is the same as '30 days'::interval.
-Ryan Kelly
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Mon, Jan 01/07/13, 2013 at 05:42:40PM +, Daniele Varrazzo wrote:
> On Mon, Jan 7, 2013 at 5:19 PM, Ryan Kelly wrote:
>
> > '1 month'::interval is the same as '30 days'::interval.
>
> No, it's not.
>
> # select '2012-07-31'::
The signal handler installed by setup_cancel_handler() will ignore
attempts to exit psql should a host be unreachable. Since the
functionality it provides won't be used until later, it doesn't make
sense to set it up so early. Therefore, move the signal handler closer
to where it is first needed.
-
33 matches
Mail list logo
