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
The following bug has been logged online:
Bug reference: 1405
Logged by: daniel
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.0
Operating system: windows xp professional
Description:instalation
Details:
error on installation
do not install
The following bug has been logged online:
Bug reference: 1460
Logged by: Daniel
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: win 2000
Description:unable dwonloads
Details:
An error has occurred processing the request...
Unable
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
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
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
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: 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
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
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
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
The following bug has been logged online:
Bug reference: 4313
Logged by: Daniel Podlejski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1, 8.3.3
Operating system: Linux
Description:Strange optimizer behaviour
Details:
cvalley_dev=# \d messages
The following bug has been logged online:
Bug reference: 4374
Logged by: Daniel Migowski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Windows
Description:pg_restore does not restore public schema comment
Details:
Hello dear
The following bug has been logged online:
Bug reference: 4375
Logged by: Daniel Migowski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: Linux
Description:pg_dump documentation, -Z option
Details:
The option documentation misses the
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-
' 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
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
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_
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
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 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
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
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: 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
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
(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
,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
>
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
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
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
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
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
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
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
Hi Guys,
Just got V7.0 and ran across a technical problem when doing initdb,
error log attached.
PS: Thanks for one of the best databases in the world!
--
Dan
We are initializing the database system with username postgres (uid=100).
This user will own all the files and must also own the
few months ago. But, in the new version of
Oracle ODBC Driver, it was fixed.
Thanks for attention
Daniel
--
Daniel Peccini
Diretor de Projetos
Mechatronic System Automação Ltda
Rua Gal. João Telles 542, Conj 902
Bairro Bom Fim - Porto Alegre
Site:www.mechsys.com.br
Fone/Fax: 51 3312 2826
The following bug has been logged online:
Bug reference: 2515
Logged by: Daniel Naschenweng
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.7
Operating system: Red Hat Linux 3.2.3-47.3
Description:Full Scan with constant column
Details:
--- BEGIN CREATE
This would greatly reduce the effords for me do use a diff on two dumps
to check for new stuff to insert. There has been a similar discussion
some years ago, so i guess that I am not the only one who would benefit
from this.
Thanks in advance,
Daniel Migowski
--
|¯¯|¯¯|Ingenieurbüro
The following bug has been logged online:
Bug reference: 2798
Logged by: Daniel Baldoni
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2rc
Operating system: Any
Description:Obsolete tiemzone data included
Details:
G'day folks,
This may not qualify
The following bug has been logged online:
Bug reference: 3289
Logged by: Daniel Kastenholz
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1, 8.2.4
Operating system: Linux, Windows
Description:SIN(PI()) expected to return 0, but returns garbage
Details
The following bug has been logged online:
Bug reference: 3548
Logged by: Daniel Heyder
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Linux (Red Hat EL4 Update 4 + PostgreSQL 8.2.4 update +
compat libraries)
Description:When quickly
The following bug has been logged online:
Bug reference: 3808
Logged by: Daniel Migowski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: Windows Server 2003
Description:Connections stays open in state CLOSE_WAIT
Details:
Hello dear bug
The following bug has been logged online:
Bug reference: 3844
Logged by: daniel birnbaum
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5-1
Operating system: windows vista
Description:will not install
Details:
when i try to install it reports a error
ed production site.
Btw. the update went without a glitch and was done in 5 Minutes, good
work for that. But I didn't know that and asking before having to
restore something for hours because of a failed update seems legitimate
to me.
With best regards,
Daniel Migowski
The following bug has been logged online:
Bug reference: 4115
Logged by: Daniel Ruoso
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: Debian GNU/Linux lenny
Description:PostgreSQL ISO format is not really ISO
Details:
ISO8601[1] defines
to have that
output option as one of the date/time output styles (name it ISO8601 or
ISO-strict), and it really doesn't need to be the default (the way pg
uses it now is nice for the human reader).
daniel
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
gnore this case, and happily send gig sized update scripts to the
server in one call the driver :).
Currently my solution is to increase the TCP buffer size in a copy of
the PGStream class, which shadows the original class in the driver jar
(bad style...).
With best regards,
Daniel Migo
PostgreSQL 7.2.1 / SUSE Linux
8.0
According to the output of "pg_ctl --help",
the -w option (lowercase)
should force the frontend to wait until the postmaster's startup completes.
Instead it prompts for a password, as with the (-W)
option (uppercase).
Ommiting the option, the frontend stil
After upgrading the database from 7.2 to 7.2.2 both relative and absolute
paths
are not accepted by either createdb or SQL-CREATE. AFAIK our provider used a
default built.
Using createdb I created databases in custom locations everal times before,
and it
worked ('datenbank/db_cluster' being the r
(english)
PostgreSQL 7.3.3 (redhat binaries)
Client pgAdmin3
Regards, Daniel
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Hi Tom,
where can i find the -n option in pg_dump. Is there any special version?
I have 7.3.3.
Regards,
Daniel
-Ursprungliche Nachricht-
Von: Tom Lane [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 1. Juli 2003 15:44
An: Curt Sampson
Cc: [EMAIL PROTECTED]
Betreff: Re: [BUGS] pg_dump -t
e the CURRENT_USER
variable passed as parameter (that would not be a big issue, of course).
Thanks for your attention,
Daniel Schreiber
--
Daniel Schreiber | ICQ: 220903493
GPG encrypted Mail welcome! Key ID: 25A6B489
Chemnitzer Linux-Tag:
http://www.tu-chemnitz.de/linu
Am Freitag, 5. September 2003 16:01 schrieb Stephan Szabo:
> On Fri, 5 Sep 2003, Daniel Schreiber wrote:
> > Hi,
> >
> > A question on IMMUTABLE functions: do they only have to return the same
> > value during a session/connection or during the databse server's
>
Am Freitag, 5. September 2003 17:05 schrieb Tom Lane:
> Daniel Schreiber <[EMAIL PROTECTED]> writes:
> > A question on IMMUTABLE functions: do they only have to return the same
> > value during a session/connection or during the databse server's
> > lifetime?
&g
compiler problem.
# select version();
version
---
PostgreSQL 7.3.2 on i386-pc-linux-gnu, compiled by GCC 2.95.4
(1 row)
# select to_date('03/06/1973','dd/mm/');
to_date
----
1973-06-03
(1 row)
This is on Debian woody with backported postgr
hat although the _lines #2 is contained by both square
and rectangle, it does not appear in both table.
I am wondering if it is a bug. Perhapes I did something wrong?
regards,
Daniel Lau
Hong Kong University of Science and Tech
Thank you for answering my question.
I made a careless mistake.
regards,
Daniel
On Mon, 22 Dec 2003, Tom Lane wrote:
> Daniel Lau <[EMAIL PROTECTED]> writes:
> > I was to extract the '_lines' (path) if the lines are contained or on by a
> > box-like polygon. Th
the user only provides the year, the date is inserted as 16.05.year,...).
Kind regards,
Daniel Struck
--
Retrovirology Laboratory Luxembourg
Centre Hospitalier de Luxembourg
4, rue E. Barblé
L-1210 Luxembourg
phone: +352-44116105
fax: +352-44116113
web: http://
On Fri, 27 Feb 2004 00:57:36 -0500
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Daniel O'Neill" <[EMAIL PROTECTED]> writes:
> > Anyway, here's the vitals, including our layout:
>
> Could I trouble you to provide those table and view definitions as an
>
11.1999"
CONTEXT: PL/pgSQL function "function_test_reg1" line 8 at assignment
retrovirology=# INSERT INTO test_reg1 (date_user) VALUES ('11:1999');
ERROR: invalid input syntax for type date: "15.11:1999"
CONTEXT: PL/pgSQL function "function_test_reg1" l
rigger_test
BEFORE INSERT OR UPDATE
ON test FOR EACH ROW
EXECUTE PROCEDURE function_test();
INSERT INTO test VALUES('2003');
Best regards,
Daniel
--
Retrovirology Laboratory Luxembourg
Centre Hospitalier de Lux
---
login_id| integer | not null
site_session_sshash | character varying(64)| not null
createtime | timestamp with time zone | default ('now'::text)::timestamp(6)
with time zone
Indexes: login_sshash_idx
Triggers: RI_ConstraintTrigger_7
This doesn't happen on a fresh initdb. In fact, it doesn't happen even
directly after I load data. It might take a day or two, but eventually
the problem manifests itself. I can reproduce it 100% of the time now.
I've noticed this on 8rc1-5. Josh and I will get you a gdb trac
,
Daniel Agut Rebollo
Departamento de eBusiness Solutions
DAVINCI Consulting Tecnológico
Tel.: +34 93.594.67.00 (Ext. 303)
Móvil: +34 630.62.03.07
Fax: +34 93.580.28.93
Email: [EMAIL PROTECTED]
Url: http://www.dvc.es
The following bug has been logged online:
Bug reference: 1529
Logged by: Daniel Wilches
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Windows XP
Description:Psql doesnt ask for passowrd
Details:
Hi,
When I just installed Postgres
The following bug has been logged online:
Bug reference: 1892
Logged by: Daniel Naschenweng
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1 beta2
Operating system: Windows
Description:pg_dumpall get five passwords
Details:
The version beta 2 get five
The following bug has been logged online:
Bug reference: 1893
Logged by: Daniel Naschenweng
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1 beta2
Operating system: Windows
Description:pg_dumpall - Search path order
Details:
When PostgreSQL make pg_dumpall
The following bug has been logged online:
Bug reference: 2260
Logged by: Daniel Blaisdell
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Gentoo Linux K:2.6.9
Description:PGCrypto Memory Problem
Details:
Prereq:
PGCrypto
Table Setup
the
server process getting killed.
Other Possibly Useful info:
CFLAGS="-O3 -march=pentium4 -pipe"
MAKEOPTS="-j3"
I'm going to try compiling with the -ssl USE flag set to avoid any
external libraries and attempt to duplicate this bug. I'll let you know
what results I
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
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: 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
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
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: 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
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
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
> 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
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
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: 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
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
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
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
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
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 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
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
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: 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: 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: 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: 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: 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
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: 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
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
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: 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
Hi Johnny,
What did you do to fix the problem?
Regards,
Daniel.
1 - 100 of 159 matches
Mail list logo
