On Fri, Aug 2, 2013 at 12:51 AM, Klaus Ita wrote:
> Isn't it a funny coincidence, that we also had a corruption of that
> same/similar type?
>
> my disk was quite confidently not tampered. I am wondering: Does PG sign, or
> checksum wal_files? Is the integrity of wal_files ensured by any mechanism
a NOTICE, that the
sequence name is not constructed as might be naively expected, would be
appropriate.
thanks and regards,
Daniel
regards, tom lane
--
*Daniel Degasperi*
Project manager
*R3 GIS* Srl - GmbH
I-39012 Merano/Meran (BZ) - Via Johann Kravogl-Str. 2
The following bug has been logged on the website:
Bug reference: 8260
Logged by: Daniel Degasperi
Email address: daniel.degasp...@r3-gis.com
PostgreSQL version: 9.1.7
Operating system: Centos 6.4
Description:
I've created a table:
CREATE
The following bug has been logged on the website:
Bug reference: 8218
Logged by: Daniel Zlatev
Email address: daniel.zla...@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: Windows
Description:
Dears,
today I was playing with some JSON data, and I
The following bug has been logged on the website:
Bug reference: 8194
Logged by: Daniel Couto
Email address: daniel.cout...@hotmail.com
PostgreSQL version: 9.2.4
Operating system: Windwos
Description:
Gostaria de saber quais são os requisitos minimos de hardware para
On Fri, Apr 12, 2013 at 7:41 AM, Tom Lane wrote:
> dan...@heroku.com writes:
>> We have a somewhat high-churn table acting as a queue, and over time it's
>> grown to be something like a gigabyte. I surmised it might be vanilla
>> bloat, but the truth seems somewhat more exotic because both VACUUM
On Fri, Apr 12, 2013 at 10:46 AM, Daniel Farina wrote:
> On Fri, Apr 12, 2013 at 7:07 AM, Andres Freund wrote:
>> On 2013-04-12 08:34:24 +, dan...@heroku.com wrote:
>>> The following bug has been logged on the website:
>>>
>>> Bug reference: 8058
&
On Fri, Apr 12, 2013 at 7:07 AM, Andres Freund wrote:
> On 2013-04-12 08:34:24 +, dan...@heroku.com wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 8058
>> Logged by: Daniel Farina
>> Email address: dan...
The following bug has been logged on the website:
Bug reference: 8058
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.0.13
Operating system: Ubuntu 10.04
Description:
We have a somewhat high-churn table acting as a queue, and over time
On Sat, Mar 30, 2013 at 8:41 PM, ajmcello wrote:
> unsubscribe
That's not how you unsubscribe from this list; you'll want to do that here:
http://www.postgresql.org/community/lists/subscribe/
--
fdr
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subs
On Thu, Mar 14, 2013 at 9:42 AM, DUBILLOT Aurelien
wrote:
> I read on your website that PostgreSQL source code is free for use and
> modification, but in my case I am working on a project where we are
> generating our own setup and we would like to integrate PostgreSQL setup
> within it.
This isn
On Fri, Feb 15, 2013 at 3:18 PM, Maciek Sakrejda wrote:
> On Fri, Feb 15, 2013 at 3:15 PM, Daniel Farina wrote:
>
>> Can you try master on xlogdump instead of the release? I have fixed a few
>> bugs there a year ago that don't seem to be in the release, and will f
On Fri, Feb 15, 2013 at 10:57 AM, Maciek Sakrejda wrote:
> On Fri, Feb 15, 2013 at 7:10 AM, Heikki Linnakangas <
> hlinnakan...@vmware.com> wrote:
>
>> Hmm, that sure looks like the same issue Kyotaro HORIGUCHI reported (
>> http://www.postgresql.org/message-id/20121206.130458.170549097.horiguchi
On Tue, Jan 22, 2013 at 10:26 AM, Tom Lane wrote:
> Heikki Linnakangas writes:
>> On 22.01.2013 15:31, jan-peter.seif...@gmx.de wrote:
>> Try:
>> CREATE EXTENSION "uuid-ossp"
>
> Although this isn't a bug, it does seem like a usability fail.
> Did we make a conscious decision not to call the exte
The second mail just has the mailing list in CC, sorry for forgetting this
before.
-Ursprüngliche Nachricht-
Von: Tom Lane [mailto:t...@sss.pgh.pa.us]
Gesendet: Mittwoch, 19. Dezember 2012 20:09
An: Daniel Migowski
Cc: pgsql-bugs@postgresql.org
Betreff: Re: [BUGS] BUG #7758: pg_dump does not corr
The following bug has been logged on the website:
Bug reference: 7753
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.1.6
Operating system: Ubuntu 10.04
Description:
Touching a trigger file will not cause promotion out of hot standby
On Fri, Nov 9, 2012 at 4:16 PM, Andres Freund wrote:
> On 2012-11-09 15:57:06 -0800, Daniel Farina wrote:
>> This is the only known occurrence to me, ever, but given it's
>> incredibly ephemeral nature probably glossed over most of the time, I
>> can't say "i
On Fri, Nov 9, 2012 at 3:35 PM, Jeff Davis wrote:
> On Fri, 2012-11-09 at 22:49 +, dan...@heroku.com wrote:
>> PGError: ERROR: could not read block 556642 in file "base/16385/2904143.4":
>> read only 0 of 8192
>
> Does that seem wildly off to you, or a little off? Do you think that
> block may
The following bug has been logged on the website:
Bug reference: 7648
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.0.9
Operating system: Ubuntu 10.04
Description:
At more or less one point in time exactly (the same second, at
-> Index Scan
using cover_attribute on "Attribute" a12 (cost=0.00..6.11 rows=1 width=8)
(actual time=0.002..0.002 rows=1 loops=2197)"
"Index
Cond: (("ObjectId" = gr."ObjectId") AND (&qu
The following bug has been logged on the website:
Bug reference: 7602
Logged by: Daniel Hedén
Email address: daniel.he...@sweco.se
PostgreSQL version: 9.2.1
Operating system: Windows 7 / Vista 64-Bit
Description:
Select with many joins against the same table is very
The following bug has been logged on the website:
Bug reference: 7510
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.1.4
Operating system: Ubuntu 10.04
Description:
Summary: Planner chooses GiST even if GIN is much better.
We have a
On Wed, Aug 15, 2012 at 5:19 PM, Tom Lane wrote:
> dan...@heroku.com writes:
>> select '1 5 hours'::interval = '1 day 5 hours'::interval;
>> ?column?
>> --
>> t
>> (1 row)
>
>> I think that the first spelling, a unit-less '1', should not be accepted.
>
> Not sure I agree. The syntax '1
The following bug has been logged on the website:
Bug reference: 7498
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.1.4
Operating system: Ubuntu 12.04
Description:
This is an expression that should probably have an error and not
The following bug has been logged on the website:
Bug reference: 7497
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.0.7
Operating system: Ubuntu 10.04
Description:
We have an interesting case of an application that is non-trivial but
On Fri, Aug 10, 2012 at 10:33 AM, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7486
> Logged by: Anderson Abreu
> Email address: andersonab...@gmail.com
> PostgreSQL version: 8.4.12
> Operating system: Linux
> Description:
>
> Dear,
>
> I'm te
On Tue, Jul 10, 2012 at 2:43 PM, Bruce Momjian wrote:
> On Tue, Jul 10, 2012 at 01:03:18PM -0700, Maciek Sakrejda wrote:
>> So, is there hope of a better fix here for 9.2 (specifically for
>> preserving extension ownership on pg_upgrade and dump/restore, though
>> I understand it may not make sens
On Jun 28, 2012 7:44 AM, "Kapil Kr. Khandelwal" wrote:
>
> Dear Team
>
>
> When I restarted the postgres9.0 service by windows then getting
following error message. Plz help me.
>
> Error Message(Error 1053) : The service did not respond start or control
requested in timely fashion.
>
> Please s
he only process connected
to a database when I want to drop it?
Regards,
Daniel Migowski
Thank you all for your explanations. I will continue this on pgsql-general.
Daniel Migowski
Von: Craig Ringer [ring...@ringerc.id.au]
Gesendet: Sonntag, 4. Dezember 2011 15:02
Bis: Daniel Migowski
Cc: pgsql-bugs@postgresql.org
Betreff: Re: [BUGS] BUG
On Sun, Nov 13, 2011 at 3:27 PM, Tom Lane wrote:
> "Daniel Farina" writes:
>> We have on hand a database that makes heavy use of the txid_snapshot family
>> of functions, and recently it just passed its 4^32 transaction mark.
>> Unfortunately, upon wraparound th
The following bug has been logged online:
Bug reference: 6291
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.0.5
Operating system: Ubuntu 10.04
Description:Xid epoch is not updated properly
Details:
We have on hand a database that
Hi Johnny,
What did you do to fix the problem?
Regards,
Daniel.
How about a warning in docs for uncautious DBA's?
2011/10/13 Bruce Momjian
>
> I assume this should _not_ be added as a TODO.
--
Daniel Cristian Cruz
クルズ クリスチアン ダニエル
Changing BEFORE DELETE to AFTER DELETE worked.
2011/10/5 Daniel Cristian Cruz
> ...
>
--
Daniel Cristian Cruz
クルズ クリスチアン ダニエル
have to be saved until end of statement."
I became a rusty DBA poluting pgsql-bugs, sorry. RTFM for myself. :)
--
Daniel Cristian Cruz
クルズ クリスチアン ダニエル
nced_id,
repetition_conf.id_repetition_conf AS reference
FROM repetition
LEFT JOIN repetition_conf
ON repetition.id_repetition_conf = repetition_conf.id_repetition_conf
WHERE repetition_conf.id_repetition_conf IS NULL;
--
Daniel Cristian Cruz
クルズ クリスチアン ダニエル
w setting null.
But the thread is almost a book, and I am confused. It's a bug or do I need
to change my schema? Where can I change it to avoid it?
--
Daniel Cristian Cruz
クルズ クリスチアン ダニエル
The following bug has been logged online:
Bug reference: 6226
Logged by: Daniel Cristian Cruz
Email address: danielcrist...@gmail.com
PostgreSQL version: 9.1.1
Operating system: "PostgreSQL 9.1.0 on x86_64-unknown-linux-gnu, compiled
by gcc (GCC) 4.1.2 20080704 (Re
The following bug has been logged online:
Bug reference: 6225
Logged by: Daniel Cristian Cruz
Email address: danielcrist...@gmail.com
PostgreSQL version: 9.1.0
Operating system: "PostgreSQL 9.1.0 on x86_64-unknown-linux-gnu, compiled
by gcc (GCC) 4.1.2 20080704 (Re
The following bug has been logged online:
Bug reference: 6200
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.0.4
Operating system: Ubuntu 10.04
Description:standby bad memory allocations on SELECT
Details:
A huge thanks to Conrad
that the WAL is
>>> safely on disk on the standby, in case the master dies. So the limit
>>> would
>>> need to be configurable.
>>
>> It seems like perhaps what we really need is a way to make replaying
>> WAL (and getting rid of now-unneeded segments) to take
The following bug has been logged online:
Bug reference: 6170
Logged by: Daniel Farina
Email address: dan...@heroku.com
PostgreSQL version: 9.0.4
Operating system: GNU/Linux Ubuntu 10.04 x86_64
Description:hot standby wedging on full-WAL disk
Details:
After seeing
;t shows up.
Naive I was trying to force Datum size to 8 and recompile postgresql for the
32 bits server. It doesn't work this way. :)
Now I request some help from some PostgreSQL Olympian Gods... :)
Regards,
--
Daniel Cristian Cruz
クルズ クリスチアン ダニエル
e not terribly
> high on your priority list, I can understand that. But if you're
> actually defending the current implementation, I'm going to have to
> respectfully disagree. It's broken, and it sucks, and this is not the
> first complaint we've had about it.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
--
Daniel Cristian Cruz
クルズ クリスチアン ダニエル
s not recommended since a schema change would crash
backups.
2011/6/3 Tom Lane
> "Daniel Cristian Cruz" writes:
> > CREATE TABLE a (
> > id_a serial primary key,
> > v text
> > );
> > CREATE TABLE b (
> > id_b serial primary key,
> > id_
The following bug has been logged online:
Bug reference: 6050
Logged by: Daniel Cristian Cruz
Email address: danielcrist...@gmail.com
PostgreSQL version: 9.0.4
Operating system: Linux
Description:Dump and restore of view after a schema change: can't
restore the
The following bug has been logged online:
Bug reference: 6035
Logged by: Daniel Schreiber
Email address: daniel.schrei...@ergora.eu
PostgreSQL version: 9.0.4
Operating system: Debian Squeeze
Description:server crash when executing recursive query (trying to
allocate
abbreviations, not just whether 'infinity' crashes.
>
> regards, tom lane
>
--
Daniel Grace
AGE, LLC
System Administrator and Software Developer
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged online:
Bug reference: 6005
Logged by: Daniel Grace
Email address: dgr...@wingsnw.com
PostgreSQL version: 9.1-beta1
Operating system: Win7 x64 (x86 postgres)
Description:ALTER ROLE ... VALID UNTIL 'infinity' crashes postm
The following bug has been logged online:
Bug reference: 5987
Logged by: Daniel Grace
Email address: dgr...@wingsnw.com
PostgreSQL version: 9.1-alpha5
Operating system: Win7 x64
Description:Rows created by WITH (INSERT ... RETURNING) are not
visible to the rest of
The following bug has been logged online:
Bug reference: 5986
Logged by: Daniel Migowski
Email address: dmigow...@ikoffice.de
PostgreSQL version: 8.3.14
Operating system: Many
Description:pg_dump output is not ordered
Details:
Hi,
I would love to give pg_dump an
The following bug has been logged online:
Bug reference: 5985
Logged by: Daniel Grace
Email address: thisgenericn...@gmail.com
PostgreSQL version: 9.1a5
Operating system: Win7 x64, also seen on Debian
Description:CLUSTER ... USING can fail with ERROR: index xxx does
The following bug has been logged online:
Bug reference: 5969
Logged by: Daniel Lyons
Email address: fus...@storytotell.org
PostgreSQL version: 9.0.3
Operating system: FreeBSD 8.2-RELEASE
Description:ecpg can't see sqlca
Details:
Under the current FreeBSD an
The following bug has been logged online:
Bug reference: 5965
Logged by: Daniel Migowski
Email address: dmigow...@ikoffice.de
PostgreSQL version: 8.3.9
Operating system: Windows 7
Description:PostgreSQL crashes during connection
Details:
Hi,
My PostgreSQL server
The following bug has been logged online:
Bug reference: 5943
Logged by: Daniel Ceregatti
Email address: dan...@ceregatti.org
PostgreSQL version: N/A
Operating system: N/A
Description:jdbc client doesn't omit pg_toast_temp tables from
schema views
Details:
I
On Tue, Feb 22, 2011 at 8:54 AM, Tom Lane wrote:
> Daniel Farina writes:
>> From what I can tell, people only see this problem with pg_dump, which
>> is interesting. This symptom has a very long history:
>
> Yeah. There seems to be some well-hidden bug whereby dropping
On Mon, Feb 21, 2011 at 10:46 PM, Daniel Farina wrote:
> It may also be useful information to know that no recent shenanigans
> have happened on this server: it's been up continuously for about 500
> days. That doesn't mean something interesting did not occur a very
>
On Mon, Feb 21, 2011 at 10:43 PM, Daniel Farina wrote:
> A medium-length story short, this query returns non-zero:
>
> select count(distinct typnamespace) from pg_type where not exists
> (select 1 from pg_namespace where oid = pg_type.typnamespace);
>
> I did a very brief
A medium-length story short, this query returns non-zero:
select count(distinct typnamespace) from pg_type where not exists
(select 1 from pg_namespace where oid = pg_type.typnamespace);
I did a very brief search in all the release notes for 8.3.5 to
8.3.14, but have not found precisely what I w
The following bug has been logged online:
Bug reference: 5842
Logged by: Daniel Popowich
Email address: danielpopow...@gmail.com
PostgreSQL version: 8.4.6
Operating system: x86_64-pc-linux-gnu (Ubuntu 10.04.1)
Description:Memory leak in PL/Python when taking slices
The following bug has been logged online:
Bug reference: 5792
Logged by: Daniel Witkowski
Email address: daniel.witkow...@gmail.com
PostgreSQL version: 8.4, 9.0
Operating system: Windows XP
Description:INSTALLER FAILS!!!
Details:
Make it usable. I tried to install
On Dec 3, 2010, at 1:49 PM, Heikki Linnakangas wrote:
> On 03.12.2010 19:48, daniel wrote:
>> I have discovered either a bug in pgcrypto (postgresql-9.0.1) or at least an
>> implementation change that is incompatible with how I've been using
>> pgcrypto. I'm hopin
onfigure --with-openssl'
I'll be happy to provide any additional information necessary and do any sort
of testing (if it should prove to be necessary) though my skills in this are
somewhat limited.
Thanks,
Daniel
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged online:
Bug reference: 5709
Logged by: Daniel Gerzo
Email address: dan...@freebsd.org
PostgreSQL version: 8.4.5
Operating system: FreeBSD
Description:PostgreSQL server 8.4.5 does not compile with gcc 4.5
Details:
This is the error
h of these conditions are true, discard one subplan and
rewrite all references to point to the other one?
Assuming it IS possible, are there any particular situations where it
wouldn't work?
On Mon, Oct 4, 2010 at 11:47 AM, Robert Haas wrote:
> On Mon, Sep 27, 2010 at 5:09 PM, Daniel Grace
The following bug has been logged online:
Bug reference: 5688
Logged by: Daniel Grace
Email address: dgr...@wingsnw.com
PostgreSQL version: 9.0.0
Operating system: Windows XP 32-bit
Description:ALTER TABLE ALTER col TYPE newtype fails if col is named
in an UPDATE OF
> Index Scan using child_pkey on wings_sky.child c (cost=0.00..40.10
rows=20 width=8)
Output: c.parent_id, c.v1, c.v2
Index Cond: (c.parent_id = $0)
Is there any chance this might be looked at in a future release?
--
Daniel Grace
AGE, LLC
System Administrator and Software Developer
dgr...@wingsnw
table2
CASCADE; etcINSERT INTO table1 VALUES blah blah ...INSERT INTO table2
VALUES blah blah ...etcCOMMIT;
Best regards, Daniel
--- On Mon, 13/9/10, Tom Lane wrote:
From: Tom Lane
Subject: Re: [BUGS] BUG #5654: Deferred Constraints don't work
To: "Daniel Howard"
Cc: pgsql-bugs@p
The following bug has been logged online:
Bug reference: 5654
Logged by: Daniel Howard
Email address: cheesero...@yahoo.com
PostgreSQL version: 8.4.4
Operating system: Linux (Ubuntu 10.04.1)
Description:Deferred Constraints don't work
Details:
The comman
The following bug has been logged online:
Bug reference: 5645
Logged by: Daniel Wagner
Email address: dt...@cam.ac.uk
PostgreSQL version: 8.4.4
Operating system: tested under Linux (Ubuntu 10.4) and Windows (7)
Description:Query Optimizer fails when it encounters an
On Fri, Jul 23, 2010 at 10:42 AM, Alex Hunsaker wrote:
> On Fri, Jul 16, 2010 at 18:04, Daniel Grace wrote:
>> However, in some circumstances Postgres will fail
>
> How exactly?
>
> Maybe its so obvious I missed it?
>
Please see BUG #5564 -- I accidentally submitt
The following bug has been logged online:
Bug reference: 5564
Logged by: Daniel Grace
Email address: dgr...@wingsnw.com
PostgreSQL version: 9.0beta3
Operating system: Windows XP 32-bit
Description:Odd behavior with aggregate_func(DISTINCT foo ORDER BY
foo)
Details
The following bug has been logged online:
Bug reference: 5563
Logged by: Daniel Grace
Email address: dgr...@wingsnw.com
PostgreSQL version: 9.0beta3
Operating system: Windows XP 32-bit
Description:Odd behavior with aggregate_func(DISTINCT foo ORDER BY
foo)
Details
On Thu, Jul 8, 2010 at 10:52 PM, Tom Lane wrote:
> "Daniel Grace" writes:
>> I apologize for not including detailed schema information. It took a lot to
>> get this to reduce to the point it did, and hopefully this is enough
>> information to find a bug.
>
The following bug has been logged online:
Bug reference: 5548
Logged by: Daniel Grace
Email address: dgr...@wingsnw.com
PostgreSQL version: 9.0beta2
Operating system: Windows XP 32-bit
Description:ERROR: invalid attnum ## for rangetable entry on
EXPLAIN VERBOSE, not
All I want to do is to delete a database, but I don't know how to actually
input the dropdb command and what other stuff I need to open...can you help?
I think my problem will be very simple for someone who understands this
--
From: "Robert Haas"
Hi Sachin:
On Wed, Dec 23, 2009 at 02:19:41PM +0530, Sachin Srivastava wrote:
> Can you post the error part of the logs (%TEMP%\install-postgresql.log)?
> Mask out any passwords (if there are any).
I have attached it. Examining the log reveals some clues that I used to
manually populate the dat
The following bug has been logged online:
Bug reference: 5253
Logged by: Daniel Convissor
Email address: dani...@analysisandsolutions.com
PostgreSQL version: 8.4.2-1
Operating system: Windows XP Pro SP3
Description:installer fails to populate data directory
Details
More info: we disabled autovacuum (we do vacuuming via cron)
and the segfaults seem to be gone.
Daniel
Tom Lane wrote:
> Nagy Daniel writes:
>> I have pg segfaults on two boxes, a DL160G6 and a DL380g5.
>> I've just checked their memory with memtest86+ v2.11
>> No e
versions, but
table contains 695 row versions
etc...
Daniel
Tom Lane wrote:
> Nagy Daniel writes:
>> I have pg segfaults on two boxes, a DL160G6 and a DL380g5.
>> I've just checked their memory with memtest86+ v2.11
>> No errors were detected.
>> We also monitor
ug_query_string
$1 = 0xb82e10 "SELECT * FROM valogatas WHERE uid!='64708' AND eletkor
BETWEEN 40 AND 52 AND megyeid='9' AND keresettnem='t' AND dom='iwiw.hu'
AND appid='2001434963' AND nem='f' ORDER BY random() DESC"
When I run
I have pg segfaults on two boxes, a DL160G6 and a DL380g5.
I've just checked their memory with memtest86+ v2.11
No errors were detected.
We also monitor the boxes via IPMI, and there are no signs
of HW failures.
Regards,
Daniel
Tom Lane wrote:
> Nagy Daniel writes:
>> I ran
27;t crash in case of
on-disk corruptions, but log an error message instead.
I'm sure that it's not that easy to implement as it seems,
but nothing is impossible :)
Regards,
Daniel
Tom Lane wrote:
> Nagy Daniel writes:
>> Here's a better backtrace:
>
> The crash l
,w2.mikor),
w1.megnezes, u.* FROM valogatas_valasz w1, valogatas_valasz w2, useradat
u WHERE w1.ki=65549 AND not w1.del AND w2.kivel=65549 AND w1.megnezes=0
AND w1.ki"...
Thanks,
Daniel
Tom Lane wrote:
> Nagy Daniel writes:
>> (gdb) p debug_query_string
>> $1 = 12099472
>
(gdb) p debug_query_string
$1 = 12099472
Now I recompiled pg with --enable-debug and waiting for a new core dump.
I'll post the backtrace and the debug_query_string output ASAP.
Please let me know if there is anything more I can do.
Thanks,
Daniel
Tom Lane wrote:
> Nagy Daniel
48 in main ()
Current language: auto; currently asm
Thanks,
Daniel
Craig Ringer wrote:
> On 10/12/2009 5:12 AM, Daniel Nagy wrote:
>> The following bug has been logged online:
>>
>> Bug reference: 5238
>> Logged by: Daniel Nagy
>> Email address: n
The following bug has been logged online:
Bug reference: 5238
Logged by: Daniel Nagy
Email address: nagy.dan...@telekom.hu
PostgreSQL version: 8.4.1
Operating system: Debian Lenny 5.0.3 x86_64. Kernel: 2.6.31.6-grsec
Description:frequent signal 11 segfaults
Details
Yesterday I ran an SQL import. It failed after 3.33 hours with following
message:
ERROR: out of memory
DETAIL: Failed on request of size 32.
** Error **
ERROR: out of memory
SQL state: 53200
Detail: Failed on request of size 32.
The log file is as follows;
2009-08-26
The following bug has been logged online:
Bug reference: 4971
Logged by: Daniel Migowski
Email address: dmigow...@ikoffice.de
PostgreSQL version: 8.3.5
Operating system: Windows XP
Description:Backend crash while doing nothing...
Details:
Hello, poor dear debuggers
Hi i downloaded the program but i cant install cause i need a password. so i
create onw buy nothing, wrong password wrong password,
8 months ago y install it the but now i cant remenber the password, i
installed in otrer computer? why cant i installed here?
Please help me
On Sat, Apr 25, 2009 at 9:52 AM, Tom Lane wrote:
> Daniel Grace writes:
> > The following nonsensical query causes PostgreSQL to fail with ERROR:
> plan
> > should not reference subplan's variable. (This was stripped down from an
> > 'useful' que
ame id (can that actually happen?
> Maybe there's more wrong with this query...), because what you
> wrote is a scalar sub-SELECT inside an aggregate call that belongs
> to the outermost query.
>
>regards, tom lane
>
--
Daniel Grace
AGE, LLC
System Administrator and Software Developer
dgr...@wingsnw.com // (425)327-0079 // www.wingsnw.com
On Fri, Apr 24, 2009 at 5:38 PM, Tom Lane wrote:
> Daniel Grace writes:
> > The following nonsensical query causes PostgreSQL to fail with ERROR:
> plan
> > should not reference subplan's variable. (This was stripped down from an
> > 'useful' que
The following nonsensical query causes PostgreSQL to fail with ERROR: plan
should not reference subplan's variable. (This was stripped down from an
'useful' query that triggered the same bug). First encountered on 8.3.4,
reproduced on 8.3.7
BEGIN;
CREATE SCHEMA bug_schema;
SET SEARCH_PATH='bug_
The following bug has been logged online:
Bug reference: 4733
Logged by: Daniel Miller
Email address: dan...@keystonewood.com
PostgreSQL version: 8.x
Operating system: N/A
Description:Feature request: add plpy.query_plan(...) to plpythonu
Details:
I have coded a
' and works, y() is written
is plpgsql and fails. Any reasons for this I do not realize?
With best regards,
Daniel Migowski
CREATE FUNCTION x() RETURNS SETOF int4 AS
$$
SELECT 1
UNION
SELECT 2
$$
LANGUAGE 'sql';
SELECT x(); -- fine with two
gesql.pid file ...] , use "sfc /scannow") worked
for me.
The error occures not allways, only in 50% of the cases.
PostgresQL Version: 8.3.3
OS: Windows Vista
Python version: Python 2.5.2
psycopg2 version: 2.0.7
The error occured when I connect to my DB wiht Python via. psycopg2.
I
The following bug has been logged online:
Bug reference: 4395
Logged by: Daniel
Email address: [EMAIL PROTECTED]
PostgreSQL version: postgresql-8.3.
Operating system: Windows Vista
Description:internal account lookup faulure
Details:
what i have do?
--
Sent via
quot;DROP SCHEMA public" in the file.
Thats why I assumed pg_restore fails here.
I haven't checked to see if a custom dump behaves differently.
Craig Ringer
I didn't check the plain text format :).
Daniel Migowski
--
Sent via pgsql-bugs mailing list (pgsql-
1 - 100 of 159 matches
Mail list logo
