Hi Groups,
I'm dealing with periodic backend process segmentation faults. I'm posting
to both the bugs and odbc lists as it seems that my application's use of
pgsqlODBC triggers a bug in the postgres backend.
The environment is:
Clients: win32 clients using various version of the psqlODBC driver
On 30 August 2012 22:42, Jeff Lake wrote:
> Lack even basic manners??
> I have been at installing this for 3 days
> manners/patience is gone!!
That's not my problem. Projecting your frustration on this mailing
list isn't cool, and, along with your poor description of the problem,
is a sure way to
Lack even basic manners??
I have been at installing this for 3 days
manners/patience is gone!!
lets see MySql works , Oracle works...
install PostgreSQL
nope it don't work, either using Command line, php, for the hell of I
tried perl
nope all fail, all segmentation fault so what would that say
On 30 August 2012 20:29, Jeff Lake wrote:
> I have looked at darn near every listing for this bug ..
> "..because curl is loaded before postgresql" << nope didn't work
> here is my system specs
This must be the worst bug report I've ever seen. I'd give the usual
link to "How to Report Bugs Effec
I have looked at darn near every listing for this bug ..
"..because curl is loaded before postgresql" << nope didn't work
here is my system specs
CentOS 5.8 64bit
24gb ram
dual i7
php 5.3.16
let yum install 8.1.4 got the error either in a php script or command line
deleted 8.1.4, rpm'd 9.1.5
On Thu, Jan 22, 2009 at 11:40:22AM +0530, Priyank Raj wrote:
> I have a code(mention below), when i run this code on Intel machine it works
> perfectly fine, but when i use AMD machine it giving me segmentation fault
> at "EXEC SQL EXECUTE IMMEDIATE :qqq;" line. what could be the problem??
Difficu
I have a code(mention below), when i run this code on Intel machine it works
perfectly fine, but when i use AMD machine it giving me segmentation fault
at "EXEC SQL EXECUTE IMMEDIATE :qqq;" line. what could be the problem??
int main(int argc,char *argv[])
{
EXEC SQL BEGIN DECLARE SECTION;
Hi,
I use PostgreSQL 7.3.2.
Choosing selection for a table I get Segmentation fault.
Namely:
1.=> \d aer_trips
uin | integer | default nextval('aer_trips_seq'::text)
l | integer |
l_type| integer |
name | text|
descr | text|
foto_trip | text|
d
I am using PostgreSQL in conjunction with PHP, and I get a
segmentation fault inside libpq. I believe the problem lies with PHP,
but the PHP developers dispute that, hence I'm reporting it here. For
details, please see http://bugs.php.net/bug.php?id=20927
Example code to reproduce the bug is at
Hi Sidney,
Cool. Really glad to hear you got it working!
Could you email the PostgreSQL "General" mailing list with that info?
It might need to be added to an FAQ or something.
:-)
Regards and best wishes,
Justin Clift
Sidney wrote:
>
> Hi Justin,
> I was using gcc 2.95.1,
>
[EMAIL PROTECTED] writes:
> sql-# \a?
> Output format is aligned.
> \a: extra argument '?' ignored
> Segmentation fault
> $ psql
7.1.1? If so, this is a minor bug that slipped into psql for about two
days at just the wrong time :-(. Update to 7.1.2.
regards, tom lane
-
Paul Mamin ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
Segmentation fault in psql
Long Description
$ psql
Welcome to psql, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help wi
Vlad Seryakov <[EMAIL PROTECTED]> writes:
> i just created new database and ran this script.
> First time the query ran okay, then i removed ps.quantity
> and re-created package_tree_view.
> After this the query crashed the server.
Hmm, I see: there's not a defense against references to
no-longer
Vlad Seryakov <[EMAIL PROTECTED]> writes:
> Is it possible to get core file, i couldn't find how to setup this.
A crashed backend should leave a core file in $PGDATA/base/YOURDB/core
If you don't see a core file in that directory, it's possible that
the postmaster was started with "ulimit -c 0"
[EMAIL PROTECTED] writes:
> Segmentation fault when changing view
I ran this script and didn't see any problem ...
In general though, whenever you drop/recreate a view you are going to
have to drop/recreate views that refer to it, too.
regards, tom lane
Vlad Seryakov ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Segmentation fault when changing view
Long Description
When i dropped column quantity in view package_tree_view, recreated this view, but
didn't recreated the view
David George <[EMAIL PROTECTED]> writes:
> Thanks. Removing sfio from configure.in and reconfiguring/making did
> the job. I didn't try it before because I figured Postgresql may have
> actually been using sfio for something.
No; I'm not sure why it's in configure's search list at all.
It soun
Tom Lane wrote:
> Uh, what are sfio and stdio anyway, and why would we want them? putc is
> in plain old libc in every system I've dealt with. If you remove both
> sfio and stdio from configure, does it work any better?
Thanks. Removing sfio from configure.in and reconfiguring/making did the
David George <[EMAIL PROTECTED]> writes:
> Here is a backtrace with debug enabled:
> (gdb) bt
> #0 0x446cc in putc ()
> #1 0x26748 in print_aligned_text (title=0x0, headers=0x746d0,
> cells=0x746e0, footers=0x746f0, opt_align=0x74700 "l",
> opt_barebones=0 '\000', opt_border=1, fout=0x68458)
Tom Lane wrote:
> Can't tell a lot from that. Could you rebuild psql with debug symbols
> so we can see a more complete backtrace?
Here is a backtrace with debug enabled:
(gdb) bt
#0 0x446cc in putc ()
#1 0x26748 in print_aligned_text (title=0x0, headers=0x746d0,
cells=0x746e0, footers=0x746f
David George ([EMAIL PROTECTED]) writes:
> (gdb) bt
> #0 0x274a8 in putc ()
> #1 0x21044 in print_aligned_text ()
> #2 0x23360 in printTable ()
> #3 0x23a44 in printQuery ()
> #4 0x18820 in SendQuery ()
> #5 0x1b044 in MainLoop ()
> #6 0x1d5a8 in main ()
> (gdb)
Can't tell a lot from that.
David George ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
segmentation fault in psql
Long Description
System info: Sparc Solaris 2.7 with GCC 2.95.2
I have compiled Postgresql 7.1RC1 without any problems.
initdb, createuser,
"Andrei N.Sobchuck" <[EMAIL PROTECTED]> writes:
> SELECT "object"."id_object" FROM "object" WHERE "status" = 1 ) AND
> ("tel" = 1 ) ) ) ) ) AND NOT(EXISTS (SELECT "po"."id_person" FROM
> "person_object" "po" WHERE (("po"."id_person" = 17 ) AND ("po"."id_object" =
> "object"."id_object" )
> "Andrei N.Sobchuck" <[EMAIL PROTECTED]> writes:
> > But one query fails when I use search on boolean field.
>
> What's the query exactly? I don't see any evidence in your backtrace
> that the function is being invoked, so I doubt that has anything to do
> with the problem.
I'm using PostgreSQL
"Andrei N.Sobchuck" <[EMAIL PROTECTED]> writes:
> But one query fails when I use search on boolean field.
What's the query exactly? I don't see any evidence in your backtrace
that the function is being invoked, so I doubt that has anything to do
with the problem.
regards
I've got a MSAccess client application. The application use ODBC to connect
to server.
Such as in my queries clauses like "some_boolean = TRUE" converts to
"some_boolean = 1",
I have to create a server procedure:
CREATE FUNCTION is_bool_eq_int(BOOL,INT4) RETURNS BOOL AS '
DECLARE
sec BOOL;
BEGIN
26 matches
Mail list logo
