On tis, 2012-05-08 at 11:33 -0400, Clay McClure wrote:
> "The gist of it is to grab python-config --prefix and store it in a
> variable, say py_prefix. If the file $py_prefix/Python exists, you are
> dealing with a Framework build and -framework Python is the
> appropriate method of linking. Otherw
On fre, 2012-05-18 at 19:57 +, erlko...@talisman.org wrote:
> The macaddr type does not allow for MACs of greater length (or less than)
> than six bytes, only capturing a particular variety of ethernet address
> (Xerox's original version) instead of the broader use of MACs where
> addresses of
On ons, 2012-05-16 at 19:55 -0500, Tulio J Carrasco wrote:
> "León", "leon", "leOn" has identical order values: none of them
> weights more for Spanish collation and PG is not working according it
> if PG makes a "second pass" that ignores collation and reorders by its
> character value.
PostgreSQ
On ons, 2012-05-30 at 23:43 +0200, Tomas Vondra wrote:
> On 30.5.2012 23:19, Tom Lane wrote:
> > I suspect it depends on how you install the new version of the library,
> > too. I would somewhat expect it to work as you're thinking if the
> > install consists of "rename old file out of the way, co
de may have contained errors, even though it was
evident to me that they actually did not. That said, it probably
wouldn't hurt to give it another try sometime soon.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sen
On fre, 2012-06-01 at 21:26 -0700, Josh Kupershmidt wrote:
> It's too bad the clang
> doesn't understand our ereport(ERROR, ...) calls don't return to the
> caller, as those seem to account for a fair bit of the spurious
> warnings. I haven't seen anything which I'd call an outright bug,
> though t
The following bug has been logged on the website:
Bug reference: 6721
Logged by: Peter Arnold
Email address: peter.arn...@jd-ag.com
PostgreSQL version: 9.0.8
Operating system: MAC OSX
Description:
Hi,
after i install PostgreSQL 9.0.8 on my MAC with OSX 10.7.4 the
change to PostgreSQL 9.1.x?
-Original Message-
From: Dave Page [mailto:dp...@pgadmin.org]
Sent: Freitag, 6. Juli 2012 10:38
To: Peter Arnold
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #6721: installation of PostgreSQL prevented WebServer
Start
On Fri, Jul 6, 2012 at 9:29 AM
On ons, 2012-07-11 at 11:32 +0200, Christian Ullrich wrote:
> 61 #: pg_basebackup.c:127
>62 #, c-format
>63 msgid " -F, --format=p|t output format (plain, tar)\n"
>64 msgstr " -F, --format=c|t|p Ausgabeformat (plain, tar)\n"
>
> pg_basebackup does not support "c" format
On tor, 2012-07-12 at 15:25 +, ch...@chrullrich.net wrote:
> The PostgreSQL configure script indiscriminately enables the --as-needed
> option to the linker if the linker supports it, which GNU ld 2.17.50 in
> FreeBSD 9 does. It does not, however, use it in its own library checks. The
> configu
On ons, 2012-07-25 at 10:08 +, jez.w...@bull.net wrote:
> When faced with a flag it doesn't recognize, xlc prints the man page.
> Thus the --version, -v, -V tests result in a particularly large
> config.log file
And is this an actual problem?
The code you are referring to is automatically ge
On Thu, 2012-08-09 at 16:26 -0500, Merlin Moncure wrote:
> Follow up on this. It is pl/sh and it is a newline issue: one of the
> developers is using a tool (I think pgadmin?) that is sticking \r
> characters at the end of every line which is throwing off pl/sh's
> shebang parsing. The issuing qu
you don't think that it is. Are you
sure that you're using the libpq distributed with 9.1.5? I don't know
much about php, but for Python, you'd do something like:
[peter@peterlaptop psycopg2]$ ldd _psycopg.so
linux-vdso.so.1 => (0x7fffbd5ff000)
libpyth
q version that actually has commit
4e816286533dd34c10b368487d4079595a3e1418, can you produce a GDB back
trace of the php process, by doing the same thing as the complainant
that posted to the php bug tracker? The process is documented here:
https://bugs.php.net/bugs-generating-backtrace.php
--
Pe
On 9/4/12 2:22 PM, Murray Cumming wrote:
> On Tue, 2012-09-04 at 10:31 -0400, Tom Lane wrote:
>> murr...@murrayc.com writes:
>>> At some point, probably in 9.1.5, the -k option to Postgres ("Unix-domain
>>> socket location" in --help), stopped accepting paths that contain spaces.
>>
>>> For instanc
On Mon, 2012-09-17 at 16:53 +, m...@suse.de wrote:
> It looks like the attempt to remove pg_upgrade's dependency on pg_config
> (http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=2815574) was
> incomplete, since contrib/pg_upgrade/exec.c still contains the line
>
> validate_exec(c
On 9/20/12 11:06 AM, Tom Lane wrote:
> Well, I would have no objection to changing pg_ctl so that it redirects
> the postmaster's stdout/stderr when a -l switch is given (actually,
> I thought it did that already...). I do object to changing the logger's
> behavior as you suggest, because that wil
dtyje6wtuy4tgdjuq6eutjjp0ctfladp9qwp8got...@mail.gmail.com
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
seems to think can cause this error
with poll(), so this seems like a slight variant of the problem
reported by Sean Chittenden (kernel resource exhaustion causes pipe
creation to fail, with unnecessarily bad consequences for Postgres).
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL
will work rather than fail.
Right. sizeof(int) is very probably 4 on all platforms that we
support. I see no problem with the proposal.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailing list (pgsql-b
x-like
systems follow LLP64 (or LLP32) in practice. sizeof(int) is 4 on
Windows (though, in contrast to LLP64, sizeof(long) is 4 too on 64-bit
windows).
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-bugs mailin
Is pgsql faster on linux?
Currently I've made an installation on W7 and the converted queries are
about 3 times slower then on mssql.
There's still some optimization to do tho...but the current results don't
look to good.
Ignore, wrong list...
My apologies..
Best,
Peter
2012/11/23 Peter Kroon
> Is pgsql faster on linux?
> Currently I've made an installation on W7 and the converted queries are
> about 3 times slower then on mssql.
> There's still some optimization to do tho...but the
ur may be astonishing, but that
doesn't make it a POLA violation. I don't have time to check now, but
I'm pretty sure that doing something else would break a whole bunch of
other common cases.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Suppor
On 1/25/13 1:35 AM, Kevin Grittner wrote:
> Peter, do you have a version that works with 9.3?
I don't, but it shouldn't be hard for someone more up to date with the
internal WAL addressing changes.
> Given that we're past the start of the last CF, do we still want to
> c
On 1/6/13 11:17 PM, funnybon...@yahoo.com wrote:
> Hello, my engish is not so good, but i try to describe what seems not to
> work. Could it be, that the LC_MESSANGES for months and days like
>
> Months
> --
> Janary=Januar
> February=Februar
>
> Days
>
> monday=Montag
> Thursdat=Dienst
Query:
SELECT
xmlelement(name s_a,
xmlagg(
xmlelement(name s_b,
xmlattributes(
sq.id AS i
),
(SELECT
xmlagg(
xmlelement(name s_c,
xmlattributes(
su.id AS i
)
)
ORDER BY table_id,id
)
FROM __table_to_table AS su WHERE su.table_id=sq.id
)
)
)
)
FROM __table AS sq
No result given in: "PostgreSQL 9.2
t" and I'm getting the
expected result.
Thanks for helping.
Best,
Peter Kroon
2013/2/19 Michael Paquier
> Hi,
>
> With your query and such tables:
> create table __table (id int);
> insert into __table values (1),(2);
> create table __table_to_table (id int, table_i
like:
"1"
"2"
"3"
etc
2013/2/19 Peter Kroon
> Hi Michael,
>
> This should have been the expected result on both machines:
> ---
>
> (1 row)
>
> I've just rebooted &
Also no result with FROM __my_table LIMIT 1;
2013/2/19 Peter Kroon
> Mm..
> The problem only occurs on a specific table in my DB.
>
> --__my_table has 512 rows
>
> SELECT * FROM __my_table; --gives me result
>
> SELECT
> --xmlagg(
> xmlelement(name el_name,
>
>Don't you have for example problems with the client application you use?
Yes, with 1 table only. I'm not getting any results.
When I'm on the sql machine via localhost or 192.168.1.100 I'm getting
results.
2013/2/19 Michael Paquier
>
>
> On Tue, Feb 19, 201
n I get
no results.
Not sure what to think of this...
2013/2/19 Peter Kroon
> >Don't you have for example problems with the client application you use?
>
> Yes, with 1 table only. I'm not getting any results.
> When I'm on the sql machine via localhost or 192.168
of course, I certainly don't know enough to know that the different
> versions of libpq don't present xmlagg output differently!
>
> The experts here will weigh in.
>
> Lou Picciano
>
>
> - Original Message -
> From: Peter Kroon
> Sent: Tue, 19 Feb 2
When there are in __table_to_table more than 88 rows nothing gets returned,
otherwise the query rolls out fine.
2013/2/19 Peter Kroon
> It appears to be a Windows issue only.
> I'll try to post some code.
>
>
> 2013/2/19 Lou Picciano
>
>> Seems your testing fro
When there are more then 88 rows in the table like 595 I can run the query
with success when using: WHERE id BETWEEN 1 AND 88;
Using LIMIT 88 fails -> returns nothing
Selecting all fails as well.
2013/2/19 Peter Kroon
> When there are in __table_to_table more than 88 rows nothin
Exceeding length 4679 is a problem. Query results(length) equal or below
this number succeed.
2013/2/19 Peter Kroon
> When there are more then 88 rows in the table like 595 I can run the query
> with success when using: WHERE id BETWEEN 1 AND 88;
> Using LIMIT 88 fails -> ret
Where can I check and/or alter this?
2013/2/19 Lou Picciano
> I wonder if there's a difference in the implementation(s) of readline
> buffering?
>
>
> - Original Message -
> From: Peter Kroon
> To: Lou Picciano
> Cc: Michael Paquier , pgsql-bugs@postg
>try to use pgAdminIII
Could you be more specific?
2013/2/19 Pavel Stehule
> 2013/2/19 Peter Kroon :
> > Where can I check and/or alter this?
>
> try to use pgAdminIII
>
> Regards
>
> Pavel
>
> >
> >
> > 2013/2/19 Lou Picciano
> >>
>you can test your queries from pgAdmin SQL executor
I have already done so.
I'll look into the logs.
2013/2/19 Pavel Stehule
> 2013/2/19 Peter Kroon :
> >>try to use pgAdminIII
> >
> > Could you be more specific?
>
> you can test your queries from pgAd
I've migrated everything to Linux and I'm able to continue my work.
I'll get back on this next week.
2013/2/19 Lou Picciano
> Sorry, Peter - I think I'd suggest something different. Start at the
> beginning; do this testing directly from the CLI (psql) on each of t
is correct using SQL, using this simple method:
https://en.wikipedia.org/wiki/EAN-13#Calculation_of_checksum_digit
We actually discussed changing the formatting of isn along the lines
you've discussed, and it was shot down. I'd just like to see it go.
--
Regards,
Peter Geoghegan
--
Sent via pgs
On 2/23/13 2:10 PM, Peter Geoghegan wrote:
> But then, contrib/isn also sanitises both ISBN
> ranges and EAN country codes using its own internal database, which
> ought to be kept in lockstep with an external database whose
> maintenance is highly decentralised - regional auth
On 26 February 2013 21:45, Peter Eisentraut wrote:
> Have each user create their custom domain?
That's likely to be the most effective solution, yes. I'd take the
fact that people haven't been complaining about contrib/isn more as
suggestive of people figuring this out f
On 2/25/13 7:59 PM, adam.tomj...@zuerchertech.com wrote:
> I have a database that uses a user-defined datatype. If the .so file
> implementing that type is missing, pg_dump will fail when dumping a table
> which uses that type, but it will still exit with status 0. The dump file
> will be truncat
On Sun, 2013-02-17 at 15:51 +0100, Christian Hammers wrote:
> The postmaster command does not list "--config-file" in its help
It is included under
--NAME=VALUE set run-time parameter
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription
On Sun, 2013-03-03 at 10:42 -0500, Tom Lane wrote:
> I think the use of str_toupper() is appropriate when processing the
> locale-specific string for a TMDAY specification; but plain DAY is not
> supposed to be locale-dependent, so we probably should use an
> ASCII-only upcasing rule in the non-TM
Just to let everyone know that I haven't forgotten this. I just don't have
any time to spend on it.
The problem still occurs.
2013/2/20 Peter Kroon
> I've migrated everything to Linux and I'm able to continue my work.
> I'll get back on this next week.
>
>
ink you're safe.
--
Regards,
Peter Geoghegan
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On 30 March 2013 14:01, wrote:
> env CFLAGS='-O3 -march=native' ./configure --with-segsize=128
Why did you build with a segment size of 128GB? Postgres binaries
built with a non-standard segment size are not widely used.
--
Regards,
Peter Geoghegan
--
Sent via pgsql-bugs
On Tue, May 14, 2013 at 2:47 PM, John R Pierce wrote:
> on a typical unix system, with one user connection active, I see 8 processes
> active at present...
To be fair, you need to use process explorer or something to see
equivalent information on Windows. Most people never will.
--
On 5/21/13 2:54 AM, Andrzej Cedro wrote:
> I use PostgeSQL 9.1 32-bit on Windows 7 Professional with Active Directory as
> LDAP.
> I have following configration in pg_hba.conf:
>
> host all all all ldapldapserver=192.168.155.157
> ldapbinddn="CN=aa,OU=b,DC=,DC=" l
On 5/21/13 3:41 AM, tudorbara...@yahoo.com wrote:
> In pg_hba.conf I have the following setup:
> hostall all laptop md5
>
> Although the hostname gets resolved by the system (LAN DNS server) I still
> get the no pg_hba.conf entry error.
Check that the following works:
$ host
On 5/21/13 6:25 PM, pol...@yahoo.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8174
> Logged by: David Johnston
> Email address: pol...@yahoo.com
> PostgreSQL version: 9.0.13
> Operating system: Ubuntu Linux 10.04
> Description:
>
>
On 5/9/13 5:40 PM, Dave Page wrote:
> Whilst working on a build issue with pl/python, I noticed an
> inconsistency in the way the server reacts to attempts to use PLs for
> which the interpreter doesn't exist. Not sure how feasible it would be
> to fix this, but the Python case doesn't seem ideal:
On 6/30/13 11:26 AM, Andres Freund wrote:
> If we would treat that warning as an error unconditionally - and I am
> not sure how easy that is given the way it's emitted - users
> encountering them, which usually will be on less common platforms, will
> have to patch configure.in to make things work
On 7/1/13 9:19 AM, Tom Lane wrote:
> AFAICT, the result in this case would be that the script comes to the
> wrong conclusion about whether ucred.h is available. Wouldn't that
> result in a build failure, or at least missing features? IOW, don't
> we need to fix this test anyway?
The test needs
On Mon, 2013-07-01 at 19:27 -0400, Tom Lane wrote:
> I think probably we'd have just not compiled the dependent code, and
> would have found out about it only when somebody complained that peer
> auth didn't work on OpenBSD. Not sure that's really a more attractive
> behavior :-(
That might be t
006ffca9 in BackendStartup (port=0x239e2b0) at postmaster.c:3304
#68 0x006fcacb in ServerLoop () at postmaster.c:1367
#69 0x006fc3c2 in PostmasterMain (argc=2, argv=0x23792a0) at
postmaster.c:1127
#70 0x006676ba in main (argc=2, argv=0x23792a0) at main.c:199
These pg_stat_st
not directly
issued by the client here.
If this is the behavior we want for SQL functions, that is something
that ought to be highlighted as a special case.
--
Peter Geoghegan
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Sun, 2013-08-25 at 12:01 -0700, Nick Carenza wrote:
> on os x 10.8.4
>
> installing with homebrew
This is not a problem. Homebrew has the appropriate patches.
There is more discussion about this issue in the mailing list archives.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgre
The changes shown below are incorrect, I think.
On 10/2/13 12:00 PM, Bruce Momjian wrote:
> *** gen_salt(type text [, iter_count integer
> *** 353,359
> 12 years
>
>
> !md5
> 2345086
> 1 day
> 3 years
> --- 358,364 ---
On Thu, 2013-10-10 at 19:14 -0400, Bruce Momjian wrote:
> > The changes shown below are incorrect, I think.
> >
> >
> > On 10/2/13 12:00 PM, Bruce Momjian wrote:
> > > *** gen_salt(type text [, iter_count integer
> > > *** 353,359
> > > 12 years
> > >
> > >
The following bug has been logged on the website:
Bug reference: 8524
Logged by: Peter Reijnders
Email address: peter.reijnd...@verpeteren.nl
PostgreSQL version: 9.1.9
Operating system: Debian Wheezy
Description:
Hai
I am implementing a postgresql database
The following bug has been logged online:
Bug reference: 4400
Logged by: Jan-Peter Seifert
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Windows xp Professional
Description:initdb doesn't work with partition D:
Details:
The following bug has been logged online:
Bug reference: 4582
Logged by: Jan-Peter Seifert
Email address: jan-peter.seif...@gmx.de
PostgreSQL version: 8.3.5
Operating system: Windows xp
Description:Renaming sequences and default value
Details:
Hello PostgreSQL-Team
Tom Lane wrote:
Thank you very much for your quick reply. I wanted to do some testing
before reporting back.
> "Jan-Peter Seifert" writes:
>> there's a problem with renaming sequences in our databases.
>
> I don't think there's really a problem here
The following bug has been logged online:
Bug reference: 4863
Logged by: Jan-Peter Seifert
Email address: jan-peter.seif...@gmx.de
PostgreSQL version: 8.4 RC1
Operating system: Windows
Description:postgresql.conf typo in log_line_prefix
Details:
log_line_prefix is
gt; requirements
The sources are included with the main postgresql sources under the
src/interfaces/jdbc directory.
Peter
--
Peter Mount [EMAIL PROTECTED]
PostgreSQL JDBC Driver: http://www.retep.org.uk/postgres/
RetepPDF PDF library for Java: http://www.retep.org.uk/pdf/
I don't have a bug template at hand.
Within a plpgsql function, concatenating TEXT strings from tables that allow NULL
values return nil results. Please run the following. The result of the second select
is nil.
Cheers, H.P.
---
create
Quoting Stanislas Pinte <[EMAIL PROTECTED]>:
>
> I confirm the bug, we experience the same. I haven't heard anything from
>
> peter too.
I've been suffering from email problems, one very sick Linux box (2 more dead
SCSI drives), and problems with both London Under
?
Also, which PreparedStatement.java are we taking about, as there are 2 of them?
Peter
>
>
> [ Charset ISO-8859-1 unsupported, converting... ]
> > "Jos? Antonio Matute Calvo" wrote:
> > >
> > > Problem:
> > > If try to use field of type &q
ling and is quite simple to
> reproduce. A simple test case can be found at:
> >
> > http://www.twospuds.com/pg7-1b3-jdbc-bug.tar.gz
> >
> > The 7.0.2 JDBC drivers work fine against the 7.1b3 backend, with a
> little tweaking for "long" rows.
> >
&
this. I've got
on my list of Saturday items the stream support, which will need this.
Peter
>
> Long Description
> org.postgresql.largeobject.LargeObject.read(byte[],int,int) returns void
> instead of int. there's therefore no reliable, non-exceptional way to
> det
uot;true" : "false");
> >
> > Why not set(parameterIndex,x.toString())?
> >
> >
> > --
> > Joseph Shraibman
> > [EMAIL PROTECTED]
> > Increase signal to noise ratio. http://www.targabot.com
> >
>
>
> --
> Bruce Momjian
return null;
> > }
> >
> 157c175
> < public void read(byte buf[],int off,int len) throws SQLException
> ---
> > public int read(byte buf[],int off,int len) throws SQLException
> 159c177,180
> < System.arraycopy(read(len),0,buf,off,len);
Quoting Barry Lind <[EMAIL PROTECTED]>:
> This is no longer a problem in 7.1. The bug here was the same one
> introduced by the wrong version of Gunner's bytearray pooling patch
> being applied. It was fixed in current sources by Peter commenting out
> the bytearray
ed.
This was the exact fix (actually it also occurs in another method as well).
> This Fix doesn't solve all problems with JBuilder4.
No, althought the current development driver is working with my copy of
JBuilder4.
Peter
--
Peter Mount [EMAIL PROTECTED]
PostgreSQL JDBC Driver: http:
Quoting "Schmidt, Peter" <[EMAIL PROTECTED]>:
> The jdbc1 driver would not compile until I modified Statement.java:
>
> [javac]
> /usr/src/postgresql-7.1beta4/src/interfaces/jdbc/org/postgresql/jdbc1/Statem
> ent.java:284: Missing term.
>
rm a setScale in the method getBigDecimal(int
> column,
> int scale)
>
> It works well for us.
Hmmm, that one slipped past me. -1 is the correct figure as the getBigDecimal
(col,scale) method handles scale==-1 as a special case.
Thanks, Peter
--
Peter Mount [EMAIL PROTE
ltSet (not sure if thats covered in the
spec) but I've seen some strange things done recently...
As for creating when the ResultSet is created - bad move. The #1 performance
hit in Java is object creation - and about 90% of all queries on average won't
involve the date/time method
I am told that the backend to postgresql will automatically
timeout and close a JDBC client connection. In, addition
the client code in JDBC connection.isClosed() will wait
up to 30 seconds (SUN Java 1.3.1) to report the connection
being closed. I normally use Oracle and the server does not
automa
uding installation of the database and creation of my db objects,
a couple of hours. This impressed me very much. I am sure
I will find further things to address but am very pleased so far.
At 11:55 AM 1/31/2002 -0500, Tom Lane wrote:
>"Peter V. Cooper" <[EMAIL PROTECTED]> writes
This is definitely not a problem with the server Tom Lane has told me
and I have verified the with my sources. It seems to be in the JDBC driver.
It only seems to happen when the JDBC client and the postgresql server
are on seperate machines and possibly on different networks.
I have further talk
>X-Sieve: cmu-sieve 2.0
>From: "Alex Cholokov" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: Bug in getTimestamp() of PostgreSQL JDBC driver?
>Date: Wed, 6 Mar 2002 15:48:20 +0700
>X-Mailer: Microsoft Outlook, Build 10.0.2627
>Importance: No
The following bug has been logged online:
Bug reference: 2496
Logged by: Heinz-Peter Heidinger
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.x
Operating system: all (Linux & Win was tested)
Description:Troubles with fixed-point types (NUMERIC, DEC
ient? What received the send from the client? The
client thinks it went out! Surely this is tcp? Apparently not! Is
there some way of saying to use tcp? I suppose insisting on ssl would
do.
Peter
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
The following bug has been logged online:
Bug reference: 3964
Logged by: Jan-Peter Seifert
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.0
Operating system: Windows xp sp2 German
Description:Parsing error in Stack Builder with LATIN1 client
encoding
The following bug has been logged online:
Bug reference: 4098
Logged by: Jan-Peter Seifert
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows xp
Description:Encoding problems
Details:
The encoding of the source db/server is LATIN1
8.0-beta2-dev3
Win2k sp4 professional
jdbc driver: pgdev.305.jdbc3
java version: 1.4
The error also occured in beta1.
The following statement executed from psql works as expected:
insert into mytable (showemail) values ('true');
--
Thanks
Mads Peter Henderson
---(end of broadc
(showemail) values ('true');
--
Thanks
Mads Peter Henderson
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
The following bug has been logged online:
Bug reference: 5874
Logged by: Jan-Peter Seifert
Email address: jan-peter.seif...@gmx.de
PostgreSQL version: 8.4.7
Operating system: Windows 7 64-Bit
Description:pg_dumpall CREATE DATABASE statements 'missing'
The following bug has been logged online:
Bug reference: 5878
Logged by: Jan-Peter Seifert
Email address: jan-peter.seif...@gmx.de
PostgreSQL version: 8.4.7
Operating system: Ubuntu 10.04 LTS
Description:BTREE_BUILD_STATS causes 'make check' to fail
Detail
The following bug has been logged online:
Bug reference: 6274
Logged by: Jan-Peter Seifert
Email address: jan-peter.seif...@gmx.de
PostgreSQL version: 9.1
Operating system: any
Description:documentation on pg_attribute.atttypmod
Details:
Hello,
it looks like that
The following bug has been logged on the website:
Bug reference: 6722
Logged by: Jan-Peter Seifert
Email address: jan-peter.seif...@gmx.de
PostgreSQL version: 9.1.4
Operating system: Windows 7 Enterprise (64-bit)
Description:
Hello,
it seems that the debugger
The following bug has been logged on the website:
Bug reference: 7820
Logged by: Jan-Peter Seifert
Email address: jan-peter.seif...@gmx.de
PostgreSQL version: 9.1.7
Operating system: Windows 7 64-bit
Description:
The statement:
'CREATE EXTENSION uuid-ossp&#
Am 22.01.2013 14:47, schrieb Marc Balmer:
> no. Your syntax is wrong.
Well - it's not exactly 'my' syntax - see:
uuid-ossp--1.0.sql
uuid-ossp--unpackaged--1.0.sql
>> I had to replace the hyphen in file names and in the scripts to make the
>> module work.
>>
> That is the wrong "fix". The hyphe
Are you using persistent connections from your application? This would hold
the connection to the database. So I think you have 2 choices:
1. Disable persistent connections
2. Increaes MAX_CONNECTIONS in postgresql.conf
From: Bakyaraj K mailto:bakya...@railsfactory.org>>
Date: Friday, May 24
The following bug has been logged online:
Bug reference: 1651
Logged by: Peter van der Meer
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7-6
Operating system: Debian Linux (Unstable)
Description:static date field is not recognized automatically when
group
After struggling with this same problem for too long, I discovered that omitting the SERVICEDOMAIN value and letting the installer set it via default did the trick. Hope this helps someone else. -Peter van der Maas > > The following bug has been logged online:> > >
The following bug has been logged online:
Bug reference: 5781
Logged by: Grant Hutchins and Peter Jaros
Email address: gr...@pivotallabs.com
PostgreSQL version: 9.0.1
Operating system: Mac OS X 10.6.4
Description:unaccent() function should be marked IMMUTABLE
Details
801 - 900 of 900 matches
Mail list logo
