The following bug has been logged on the website:
Bug reference: 8170
Logged by: Chris Travers
Email address: chris.trav...@gmail.com
PostgreSQL version: 9.2.4
Operating system: Debian Linux
Description:
I have a pl/pgsql function which calculates at imestamp and
Devrim,
Thanks for the super fast fix!
Chris
On Feb 8, 2013, at 5:56 PM, Devrim GÜNDÜZ wrote:
>
> Hi,
>
> Thanks again for the report. I committed changes. Packages will appear
> in less than 4 hours.
>
> Regards, Devrim
>
> On Thu, 2013-02-07 at 20:22 +,
The following bug has been logged on the website:
Bug reference: 7857
Logged by: Chris Meisinger
Email address: chris.meisin...@centro.net
PostgreSQL version: 9.1.8
Operating system: CentOS 6.3
Description:
1. Provision a fresh machine (CentOS 6)
2. Perform a yum
On Tue, Dec 11, 2012 at 1:37 AM, Magnus Hagander wrote:
> On Sat, Dec 8, 2012 at 2:41 PM, wrote:>
> The following bug has been logged on the website:
>>
>> Bug reference: 7744
>> Logged by: Chris Jerdonek
>> Email address: chris.jerdo...@gmail
The following bug has been logged on the website:
Bug reference: 7744
Logged by: Chris Jerdonek
Email address: chris.jerdo...@gmail.com
PostgreSQL version: 9.2.2
Operating system: Mac OS X
Description:
This section of the docs:
https://docs.djangoproject.com/en/1.4
create a different timeline?
Best Wishes,
Chris Travers
d above.
This is one of those reasons I don't see the backwards-compatibility
reasons so convincing. We can't create some modicum of consistency in
behavior without breaking *something.* I think the big issue is that
nobody has figured out exactly what we want to break.
Best Wishes,
Chris Travers
constraint, you'd probably have to go
> looking around for type_constraints() though.
>
> merlin
>
I suppose this is yet another reason why multiple inheritance is an
absolutely killer feature in PostgreSQL is that currently you *can* model
your data in an equivalent way *and* have check constraints and not null
constraints enforced ;-)
Best Wishes,
Chris Travers
in ALTER TABLE and much more about documenting the chosen
> behavior. I think the reason you're confused by the proposed TODO
> wording is exactly that it uses the phrases "TYPE features" and "TABLE
> features" as if those concepts were defined or documented anywhere.
>
To be honest, having worked with these a bit, I think we need to choose the
behavior before we can document or even implement it.
Best Wishes,
Chris Travers
ange without notice.
Maybe worth bringing up on the docs list. I don't mind the fact that
behavior is undefined in some cases. However, it might be a good idea to
let people know that they are moving into "we won't commit not to breaking
your app even if you get this to work" territory.
Best Wishes,
Chris Travers
On Fri, Aug 24, 2012 at 3:52 AM, Amit Kapila wrote:
> From: pgsql-bugs-ow...@postgresql.org
> [mailto:pgsql-bugs-ow...@postgresql.org] On Behalf Of Tom Lane
> Sent: Friday, August 24, 2012 10:33 AM
> Chris Travers writes:
>>> My guess is that tableoid is not known when th
Hi;
I figured I would report this as well, primarily because people
getting into table inheritance may try to use this to solve the set
exclusion problem (i.e. partly required to prevent duplicate key
values in an inheritance tree). I see this as minor because I don't
see a lot of people using th
On Wed, Aug 22, 2012 at 8:04 AM, Tom Lane wrote:
> Chris Travers writes:
>> It's when we add group by that things appear broken. Note it starts
>> returning 196 (14 x 14) records, which suggests a cross join against
>> itself.
>
>> mtech_test=# explain an
table | postgres | sql | SELECT * FROM
account_heading order b
y accno; | Returns a list of all account headings, currently ordered
by account
number.+
| | |
|
|| | |
|
The following bug has been logged on the website:
Bug reference: 6732
Logged by: Christian Ullrich
Email address: ch...@chrullrich.net
PostgreSQL version: 9.1.4
Operating system: FreeBSD 9
Description:
PostgreSQL 9.1 does not build on FreeBSD 9 if --enable-nls and a H
:
checking for uuid_export in -lossp-uuid... no
checking for uuid_export in -luuid... yes
...
checking uuid.h usability... yes
checking uuid.h presence... yes
checking for uuid.h... yes
go figure ... ;).
best regards,
chris
--
chris ruprecht
database grunt and bit pusher extraordinaíre
On May 31
The following bug has been logged on the website:
Bug reference: 6641
Logged by: Chris Ruprecht
Email address: ch...@cdrbill.com
PostgreSQL version: 9.1.3
Operating system: Mac OS X 10.7.4
Description:
running configure as such:
export MACOSX_DEPLOYMENT_TARGET=10.7
On 20 February 2012 21:23, Tom Lane wrote:
> I wrote:
>> Chris Rees writes:
>>> On 18 Feb 2012 18:49, "Tom Lane" wrote:
>>>> https://redports.org/browser/crees/databases/postgresql91-server/files/patch-config-python-m4
>
>>>> I think we&#x
FreeBSD, and none of them have shown any sign of not
> liking threaded python:
> http://buildfarm.postgresql.org/cgi-bin/show_status.pl
>
> I think we'd need more information before arbitrarily disabling this.
The patch is to disable the error! It says that threaded python is
absolutely fine for FreeBSD; the check has been removed in the FreeBSD port
for a while, anyway.
Chris
The following bug has been logged online:
Bug reference: 6217
Logged by: Chris Gernon
Email address: kabi...@gmail.com
PostgreSQL version: 9.1.0
Operating system: Windows XP
Description:to_char() gives incorrect output for very small float
values
Details:
The
On Fri, Jul 1, 2011 at 10:35 PM, Tom Lane wrote:
>
> "Chris Bandy" writes:
> > While using the information_schema to examine my tables, I found that
> > "columns"."column_default" does not consistently represent the DEFAULT
> > constraint
The following bug has been logged online:
Bug reference: 6080
Logged by: Chris Bandy
Email address: bandy.ch...@gmail.com
PostgreSQL version: 9.0.3
Operating system: Gentoo
Description:information_schema.columns.column_default contains NULL
inconsistently
Details
The following bug has been logged online:
Bug reference: 5981
Logged by: Chris Price
Email address: cjpr...@bigpond.net.au
PostgreSQL version: 9.0.3
Operating system: Winders Server 2008 R2 Standard
Description:Attempt to install language pltcl fails on 64-bit
The following bug has been logged online:
Bug reference: 5964
Logged by: Chris Curvey
Email address: ch...@chriscurvey.com
PostgreSQL version: 9.0.3
Operating system: Linux (ubuntu 10.10 server 64-bit)
Description:doc bug -- copy does not take "format&quo
The following bug has been logged online:
Bug reference: 5854
Logged by: Chris R.
Email address: chri...@gmx.net
PostgreSQL version: 9.02
Operating system: CentOS 5.5
Description:base64 decode returns bytea and no text
Details:
There is a break in how pg9.0 handles
t...@sss.pgh.pa.us (Tom Lane) writes:
> https://issues.apache.org/jira/browse/JUDDI-374
There's an issue that JDBC doesn't cope very well with 'Infinity'
values, which is more or less the opposite of what's reported here. I
have been tending to put "don't allow +/-Infinity" constraints onto
time
> Date: Mon, 11 Oct 2010 16:15:52 -0700> From: pie...@hogranch.com> To:
> sgl...@hotmail.com> CC: pgsql-bugs@postgresql.org> Subject: Re: [BUGS]
> pg_dumpall -> by hand without --binary-upgrade or BUG #5690: pg_upgrade
> fails> > On 10/11/10 4:09 PM, Chris E
LOG: received fast shutdown request2010-10-11 17:34:58 EDT LOG:
aborting any active transactions2010-10-11 17:34:58 EDT LOG: autovacuum
launcher shutting down2010-10-11 17:34:58 EDT LOG: shutting down2010-10-11
17:34:58 EDT LOG: database system is shut down
And there we sit, dejected. Any thoughts would be greatly appreciated.
Chris English
On 09/28/2010 01:17 PM, Tom Lane wrote:
Chris Ross writes:
When there is a table (or view, or sequence) of the same name in one
schema as another, and both of these schemas are in the set search_path,
only the first schema in the search path will show that name in the
output of \d[S
On 09/29/2010 02:08 PM, Chris Ross wrote:
On 09/28/2010 01:17 PM, Tom Lane wrote:
That's the intended behavior, because only the first one is actually
accessible without schema-qualifying its name. You can use a pattern
of "*.*" if you want to see objects that are hidden accordin
o help describe the problem.
- Chris
% \i pgsql9.bugshow-database.sql
% \d
List of relations
Schema | Name | Type | Owner
+--+---+---
test2 | test_table | table | cross
test2 | test_
mission-critical, I think it is a good practice to
do what the Pg developers do and avoid making unnecessary changes
within a stable release. This means that some "bugs" should be
treated as "features" where the behavior is longstanding, a workaround
is possible, and the fix
Just adding my voice to the "fix it" camp. Is there any reason the
table scans in this sort of thing cannot be independently planned?
Best Wishes,
Chris Travers
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.post
mamf...@gmail.com (Michael Felt) writes:
> I have just run compiled postgres on AIX (AIX 5.3, pgsql version 8.4.4) and
> have a few surprises regarding the make process.
>
> 1. Very nice - it found gmake as /usr/local/bin/make and called GNUmakefile
> 2. The make completes and it starts a test.
> -
46.77b9,16,,2010-08-06
09:48:22 CEST,,0,LOG,0,"consistent recovery state reached at 5B/
DD00",""
2010-08-06 09:48:31.751 CEST,,,30649,,4c5bbe46.77b9,17,,2010-08-06
09:48:22 CEST,,0,LOG,0,"restored log file
""0001005B00DD"" from arch
The following bug has been logged online:
Bug reference: 5602
Logged by: Chris
Email address: christoph.sprin...@magicinternet.de
PostgreSQL version: 9.0beta3
Operating system: Debian 5.0.3
Description:Recovering from Hot-Standby file backup leads to the
currupted
kan...@us.ibm.com ("Denise Kanyuh") writes:
> The following bug has been logged online:
>
> Bug reference: 5567
> Logged by: Denise Kanyuh
> Email address: kan...@us.ibm.com
> PostgreSQL version: 8.0.15
> Operating system: AIX 7.1
> Description:will not install
> Detail
alvhe...@commandprompt.com (Alvaro Herrera) writes:
> Excerpts from Chris Browne's message of jue jun 24 14:40:30 -0400 2010:
>> robertmh...@gmail.com (Robert Haas) writes:
>> > This patch makes it clear that the workaround is no good on AIX 6.1,
>> > but it doesn&
robertmh...@gmail.com (Robert Haas) writes:
> This patch makes it clear that the workaround is no good on AIX 6.1,
> but it doesn't seem quite clear about whether the underlying problem
> has been fixed in AIX 6.1. It would be good to understand that.
Better?
--
(format nil "~...@~s" "cbbrowne"
pie...@hogranch.com (John R Pierce) writes:
> On 06/23/10 6:02 PM, Chris Browne wrote:
>> There is already an FAQ on issues relating to AIX. It is, in recent
>> versions, part of the documentation tree:
>>
>> <http://www.postgresql.org/docs/9.0/static/installation-pla
we...@sg.ibm.com (Liang Giap Wee) writes:
> Hi,
> We are considering using your open source Postgres on AIX5.3 and AIX6.1.
> May i know if you have a opensource community to help with support issues
> should we face problem with during installation? Thanks...
> Regards,
> Liang Giap, Wee
There is
Heikki,
Thanks for your help on this issue.
I modified my restore script to return 1 only once and that solved the
problem.
Cheers,
Chris
On Fri, May 7, 2010 at 3:35 AM, Heikki Linnakangas <
heikki.linnakan...@enterprisedb.com> wrote:
> Chris Copeland wrote:
> > I have two s
The following bug has been logged online:
Bug reference: 5452
Logged by: Chris Copeland
Email address: ch...@cope360.com
PostgreSQL version: 8.2.16
Operating system: Solaris 10 x86
Description:Server core dumps coming out of recovery mode
Details:
I originally had
Hi Chris,
Many thanks for your comments.
On Mon, Apr 5, 2010 at 10:16 AM, Chris Browne wrote:
> Indeed.
>
> You can only be certain of there actually being a conversion if the
> transaction directly involved a conversion between currencies.
>
> Thus...
>
> 1. If I buy
to...@tuxteam.de writes:
> On Fri, Apr 02, 2010 at 10:18:24AM -0700, Chris Travers wrote:
>
>> Suppose I live in Canada and I have two checking accounts for my
>> business, one in CAD and one in USD. In essence I have to account for
>> a floating balan
On Fri, Apr 2, 2010 at 9:51 AM, Dimitri Fontaine wrote:
>> One could also then store monetary[] arrays for addressing specific
>> denomination storage. I.e. "When closing the till we had 26 pennies,
>> 53 nickles, 12 quarters, 25 $1 bills, 35 $5 bills, 15 $10 bills, and 5
>> $20 bills."
>>
>> Th
On Tue, Mar 30, 2010 at 12:22 PM, Kevin Grittner
wrote:
> [Did you mean to take this off-list, or was that accidental?]
Accidental.
>
> Chris Travers wrote:
>
>> With due respect, this sort of thing is rather difficult to get
>> right all at once.
>
> Division
on of this
that would require 8.4 or higher. It might come in handy for
LedgerSMB too.
Best Wishes,
Chris Travers
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
7;t sound like a bug, though. Here are a few
questions though to say for sure:
1) This is Windows, right? Which version?
2) You say you "deleted" it. How? What exactly did you do to delete it?
3) Can you try again and copy the full error messages here?
Best Wishes,
Chris Travers
On Wed, Mar 10, 2010 at 8:20 AM, Robert Haas wrote:
> On Tue, Mar 9, 2010 at 11:02 AM, Tom Lane wrote:
>> We may need to document it, but not like that; it's (a) incorrect and
>> (b) unhelpful to the reader, who is left without any clear idea of what
>> to avoid. I think that the real issue here
make
comparisons problematic. In some cases you may need to properly cast
NEW and OLD prior to making comparisons.
Best Wishes,
Chris Travers
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
record is greater
than in the row). This seems to be separate from the question of
whether ROW(NULL...) and NULL are the same from a row comparison
viewpoint.
Hope this adds something to the discussion.
Best Wishes,
Chris Travers
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Textual representations are not necessarily
consistent.
I guess a better question for Oleg might be:
"Why is it important to you to get this fixed? What are you trying to
do that you can't do without fixing this?"
Best Wishes,
Chris Travers
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
> If you don't provide more details (test case) it's hard to say if it's a bug
> or not.
Is that a pg-Admin bug report? If so, consider sending it to the
email lists of that project.
Best Wishes,
Chris Travers
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql
s
may have improved since I was supporting it but it used to be quite
common that it would cause weird behavior in applications) I
personally think the stack trace is likely to be the best way to test
where the problem is.
Best Wishes,
Chris Travers
--
Sent via pgsql-bugs mailing list (pgs
ngrossed in development on the
project) to submit a patch for :-)
Best Wishes,
Chris Travers
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Wed, Feb 3, 2010 at 11:30 AM, Robert Haas wrote:
> Quoting an identifier also makes it case-sensitive, whereas unquoted
> names are always folded to lower case. For example, the identifiers
> FOO, foo, and "foo" are considered the same by PostgreSQL, but "Foo"
> and "FOO" are different from th
; SELECT col1 FROM myTABLE
>
> SELECT Col1 FROM myTable
>
> please, may you help ?
I thought PgSQL was case insensitive by default and that both those
would be executed as:
SELECT col1 FROM mytable;
If you are seeing otherwise in the manual, can you provide a section?
Best Wishes,
QL problem, and it certainly isn't a Pg
bug. It has to do with changes to the Readline library and the way
linking works on Linux systems.
In general, the word of advice is that unless you know what you are
doing, don't try this at home.
Best Wishes,
Chris Travers
--
Sent via pgsql-bugs
The following bug has been logged online:
Bug reference: 5291
Logged by: Chris Arensdorf
Email address: chris.arensd...@gdc4s.com
PostgreSQL version: 8.4.2
Operating system: Linux RedHat 5.3
Description:Password change restrictions
Details:
I would like to make an
ed is that the old way simply didn't work for
> any significant use of the dependency info. Just ignoring the
> dependencies, as your patch effectively proposes, is going to lead to
> restore failures or worse.
Just to clarify, the only part that would not be supported would be
the paral
ared to work in pre-8.3 but may
have done the wrong thing. Definitely quote your literals.
Best Wishes,
Chris Travers
--
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: 5252
Logged by: Chris
Email address: lk7...@hotmail.com
PostgreSQL version: 8.3.5
Operating system: Linux
Description:postgresql-8.3.5.tar.gz does not exist any more
Details:
Hi there,
It seems that the
On Wed, Dec 16, 2009 at 7:07 PM, Tom Lane wrote:
> Chris Travers writes:
>> It looks like this could be added without a disruption to programmer
>> interfaces, but it seems like any major change in this area would
>> create binary compatibility issues (i.e. requir
Just to be clear (before I consider attempting a patch maybe I can
hand off to someone else to double-check)...
On Wed, Dec 16, 2009 at 5:31 PM, Tom Lane wrote:
> Yeah. The problem is that the only infrastructure libpq has for returning
> individual error message fields (like the SQLSTATE) is a
ppy to try to
write a patch but you probably don't want my C code in your library.)
Best Wishes,
Chris Travers
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Wed, Dec 16, 2009 at 1:39 PM, Tom Lane wrote:
> Chris Travers writes:
>> trying again. Sorry for the duplicate.
>> On Wed, Dec 16, 2009 at 1:12 PM, Tom Lane wrote:
>>> Exactly what "frontend" are you talking about here? Because what this
>>> sou
trying again. Sorry for the duplicate.
On Wed, Dec 16, 2009 at 1:12 PM, Tom Lane wrote:
> "Chris Travers" writes:
>> I am noticing that that a failed database connection results in an unusable
>> SQLSTATE in libpq, and a very different SQLSTATE than the backend
>&
On Wed, Dec 16, 2009 at 12:35 PM, Kevin Grittner
wrote:
> "Chris Travers" wrote:
>
>> I am noticing that that a failed database connection results in an
>> unusable SQLSTATE in libpq, and a very different SQLSTATE than the
>> backend registers.
>
> Wel
The following bug has been logged online:
Bug reference: 5246
Logged by: Chris Travers
Email address: chris.trav...@gmail.com
PostgreSQL version: 8.1.18
Operating system: Fedora Linux 12
Description:Misleading/inconsistent SQLSTATE behavior
Details:
Hi all;
I am
The following bug has been logged online:
Bug reference: 5195
Logged by: Chris Arensdorf
Email address: chris.arensd...@gdc4s.com
PostgreSQL version: 8.1.4
Operating system: Linux RedHat 5.3
Description:PKI Certificate Authentication Implementation
Details
t...@sss.pgh.pa.us (Tom Lane) writes:
> "Christian DUPONT" writes:
>> I use slony 1 v 1.2.14.
>> After an unexpected stop, several tables remained locked :
>
> Is it possible that the locks are being held by a prepared transaction?
> Next time it happens, look into the pg_prepared_xacts status vi
The following bug has been logged online:
Bug reference: 5101
Logged by: Chris Mikkelson
Email address: cm...@qwest.net
PostgreSQL version: 8.4.1(+earlier)
Operating system: all
Description:Off-by-one error in bitncmp() in
src/backend/utils/adt/network.c
Details
Andreas writes:
> Heikki Linnakangas schrieb:
>> andreas wrote:
>>> if nextval is used inside a function in a insertstatement, you get always
>>> the value from inside the last function. but i expected, that lastval()
>>> deliver the value from the insertstatement. i think, this should
>>> clearif
mvazq...@mx1.ibm.com (Manuel G Vazquez B/Mexico/IBM) writes:
> I have a customer who bought an IBM
> Power Systems, running AIX 5.3 and wants to install the face="Arial">PostgresSQL
> 8.1.9. Can you pls tell me where I can Download this version for AIX? and
> if youa have some documentation or FAQ
> yet you propose dumbing down the database even farther, without any hope
of ACID
> compliance, without any transactional integrity, indeed, without even
really being
> relational ?
> at least, thats what I get from my first read of it.
OK so you are a theorist/perfectionist, I can respect
ge the gap between Postgres' architecture and the
architecture of cloud computing.
I wrote a "thought paper" on how this might be accomplished:
http://markmail.org/message/u6wpqhz2ypxdyvtk
- chris
The following bug has been logged online:
Bug reference: 4560
Logged by: chris wood
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3RC2
Operating system: debian
Description:bug 4528
Details:
Hi, I reported bug 4528 some time ago (timezone problem). In the
The following bug has been logged online:
Bug reference: 4528
Logged by: chris wood
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.4
Operating system: Debian
Description:(rounding?) error with some timezone names
Details:
again sorry I do not have access
I apologize in advance for not testing on 8.3.5, but that would be very
difficult for me.
here is where it works in 8.3.1:
protocalte=> select version() ;
version
Pos
The following bug has been logged online:
Bug reference: 4525
Logged by: chris wood
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.4
Operating system: Debian
Description:substring with this pattern works in 8.3.1; does not
work in 8.3.4
Details:
I
ep 19 11:30 0013
-rw--- 1 26 26 262144 Sep 19 11:40 0014
-rw--- 1 26 26 262144 Sep 19 11:49 0015
Chris Barnes
Recognia Inc.
Operations and Database Administration..
[EMAIL PROTECTED]
613.789.2267 ex.260
Empowering Traders!
This email and/or any do
[EMAIL PROTECTED] ("Janardhanachari, Jagadeesha") writes:
> What is the password for postgres ?
This isn't a bug, to be sure, and there isn't a password declared, by
default.
The account that is created, initially, by default, has *no* password,
which means you must connect via some means that d
Hi,
Would you please tell me if there is a default password for the Postgres vacuum
utility?
Thank you,
Chris Schroter
--
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: 4173
Logged by: Chris West (Faux)
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: linux (debian lenny)
Description:Illogical error message with aggregates + order by
Details
[EMAIL PROTECTED] (Gregory Stark) writes:
> "Dave Page" <[EMAIL PROTECTED]> writes:
>
>>> Wrong tip at the beginning of the administrator: "The answer to the
>>> question of Life, the Universe and Everything is 42." The answer is "God
>>> created them."
>>
>> I'm not so sure - can you define exactl
On Jan 25, 2008 2:30 PM, Chris Hoover <[EMAIL PROTECTED]> wrote:
> On Jan 25, 2008 2:23 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> > "Chris Hoover" <[EMAIL PROTECTED]> writes:
> > > In the noon log, I have this entry:
> > > 2008-01-25 12:
On Jan 25, 2008 2:23 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Chris Hoover" <[EMAIL PROTECTED]> writes:
> > In the noon log, I have this entry:
> > 2008-01-25 12:00:00.063 EST,,,3040,,479a01f1.be0,2,,2008-01-25 10:36:17
> > EST,,0,LOG,0,"sy
this happened.
>
> Best regards,
>
> On Jan 24, 2008 12:37 PM, Chris Hoover <[EMAIL PROTECTED]> wrote:
>
> >
> > The following bug has been logged online:
> >
> > Bug reference: 3901
> > Logged by: Chris Hoover
> > Email address:
The following bug has been logged online:
Bug reference: 3900
Logged by: Chris Hoover
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.rc2
Operating system: RHES 4.0
Description:0 byte .log files created when not using strerr
Details:
I am using the syslog
The following bug has been logged online:
Bug reference: 3901
Logged by: Chris Hoover
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.rc2
Operating system: RHES 4.0
Description:Received error
Details:
I just received this error on my command line. I think
The following bug has been logged online:
Bug reference: 3830
Logged by: Chris
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3beta4
Operating system: Windows Vista Home Premium
Description:Error during Installation (german)
Details:
Hello Postgres-Team,
i
Hi, I found this bug? In beta 3. I am not a Linux guru so installing any
betas in Debian is very painful for me. Perhaps you could check to see if
it is still there in beta 4??
Last time I reported a bug
http://archives.postgresql.org/pgsql-committers/2007-11/msg00584.php
I did not get any d
Plpgsql procedure:
BEGIN
Drop table if exits temptable cascade ;
Create temp table temptable ...
Create temp view tempview as select . from temptable...
Select .. from tempview ...
END
The first time I run this after I create the procedure it works perfectly.
The second time
The following bug has been logged online:
Bug reference: 3738
Logged by: Chris Vickery
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: OS X 10.4
Description:psql crashes on exit.
Details:
senate=# \q
psql(4484) malloc: *** error for
[EMAIL PROTECTED] writes:
> I have a problem with the installation: Data directory error:
>
> The PostgreSQL Data directory Must be on an NTFS formatted Volume
In which way does this appear to be a bug?
Is the volume you are trying to put the database on an NTFS-formatted
one, and the system is n
this sort of
issue to start on.
Best WIshes,
Chris Travers
begin:vcard
fn:Chris Travers
n:Travers;Chris
email;internet:[EMAIL PROTECTED]
tel;work:509-888-0220
tel;cell:509-630-7794
x-mozilla-html:FALSE
version:2.1
end:vcard
---(end of broadcast)---
[EMAIL PROTECTED] ("Vova") writes:
> The following bug has been logged online:
>
> Bug reference: 3583
> Logged by: Vova
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.7
> Operating system: Linux Gentoo
> Description:IMPORT/EXPORT into PostgreSQL
> Details
The following bug has been logged online:
Bug reference: 3450
Logged by: Chris Bowlby
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.11
Operating system: SUSE Linux Enterprise Server 9 SP2
Description:Multiple Stored procedure calls cause issue with temp
[EMAIL PROTECTED] ("Sridhar Sourirajan") writes:
> Is PostgreSQL supported on these UNIX platforms. When I go to
> www.postgresql.org, I only see binary downloads for Linux and
> Win32. How about for these other flavors of Unix? Thank you!
On the traditional commercial UNIX(tm) flavours, you'll ne
1 - 100 of 177 matches
Mail list logo
