Thanks!
On 28 November 2011 14:30, Tom Lane wrote:
> Belinda Cussen writes:
> > I've managed to produce this fault consistently now.
> > Below is the simplified code:
>
> > CREATE TABLE foo_1 (id int primary key,media_uri TEXT);
> > INSERT INTO foo_1(id) SELE
115
#32 0x7f97113fc693 in main (argc=7, argv=0x7f97138a5330) at main.c:199
On 28 November 2011 04:16, Tom Lane wrote:
> Belinda Cussen writes:
> > The code works ok on my database too when I call the procedure only once
> > sequentially. I hit the segmentation fault consistently
nking there may some corrupted data or is it possible to be the
table size?
Again, thanks for your help.
regards
Belinda
On 25 November 2011 08:09, Belinda Cussen wrote:
> Hi Pavel,
> Thanks for you help.
> The code works ok on my database too when I call the procedure only once
&
esn't cause a crash.
Any ideas?
regards
Belinda
On 24 November 2011 21:57, Pavel Stehule wrote:
> Hello
>
> This is not known bug - there should be bug in PostgreSQL or your database
> (data files) can be broken.
>
> 2011/11/24 Belinda Cussen
>
>> Hi there,
>&
ue_ie
ON activity (venue_id );
--
[image: Servian Logo]*Belinda Cussen* | Servian Pty
Ltd<http://www.servian.com.au/> |
*m:* 0466 309 169 | *t:* 02 9376 0700 | f*:* 02 9376 0730
