The following bug has been logged online:
Bug reference: 4932
Logged by: Peter Much
Email address: p...@citylink.dinoex.sub.org
PostgreSQL version: 8.4.0
Operating system: FreeBSD 7.2
Description:Upgrade 8.2.13 -> 8.4.0 - Kerberos option missing
Details:
In chap
Dear Magnus!
On Wed, Jul 22, 2009 at 11:52:32AM +0200, Magnus Hagander wrote:
! On Wed, Jul 22, 2009 at 11:42, Peter Much wrote:
! > In chapter 19.3.5 of the manual an option "krb_server_hostname" is
! > mentioned.
! > This option was present in 8.2 but is no longer present
On Wednesday 29 July 2009 01:57:50 Jim Michaels wrote:
> it is impossible to compile in libpq headers unless the installation
> directory for postgres has no spaces. compilers such as gcc/mingw don't
> like that.
Proof please?
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To m
On Wednesday 29 July 2009 11:39:03 Giorgio Valoti wrote:
> I get a crash when I invoke xml function like xml_is_well_formed.
>
> It works with static xml but not if it’s dynamically generated.
>
> It crashes even if I first create the xml dynamically and then invoke the
> function with static text.
On Monday 10 August 2009 03:41:06 Richard Neill wrote:
> * Division of a timestamp by an interval should result in something
> dimensionless.
What would be the semantics of this? What's today divided by 2 hours?
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to
On Friday 14 August 2009 02:32:38 Jim Michaels wrote:
> The following bug has been logged online:
>
> Bug reference: 4985
> Logged by: Jim Michaels
> Email address: jmich...@yahoo.com
> PostgreSQL version: 8.4.0
> Operating system: XP Pro Sp3
> Description:LIMIT documen
On tor, 2009-08-20 at 20:24 +, Brian Ceccarelli wrote:
> since the < and > comparison operators seem to be case insensitive:
>
> select 'a' < 'Z';-- true
> select 'a' < 'z';-- true
> select 'A' < 'Z';-- true
> select 'A' < 'z';-- true
>
> select 'z' < 'A';-- false
> select
On mån, 2009-08-24 at 20:10 +0100, Greg Stark wrote:
> It's completely email based so we could just treat it as a mailing
> list without having to go visit a web interface to stay up to date. We
> could add CVS/whatever hooks so whenever a commit message says it
> closes a bug it gets closed automa
On mån, 2009-08-24 at 23:07 +0100, Greg Stark wrote:
> I think it's a conceit to think we always fix bugs immediately.
I completely agree with that one. The claim that we don't need a bug
tracker because most bugs get fixed immediately is bogus because a) it's
not true, and b) it doesn't help peo
On mån, 2009-08-24 at 19:56 -0400, Tom Lane wrote:
> Alvaro Herrera writes:
> > Personally I still think debbugs would suit us perfectly, but 1. I don't
> > have time to handle it, 2. nobody else believes this, 3. the debbugs
> > developers are not very interested in helping us use it.
>
> What i
On tor, 2009-09-03 at 20:53 +, Raja Rayaprol wrote:
> I would like to know if there is demand for similar functionality from
> Postgres users, and whether PostgreSQL Plus (or other variant) offer
> any
> relief in this area ?
This doesn't appear to be a bug. You might get better feedback fro
On Sun, 2009-09-20 at 01:00 +, Paulo wrote:
> like to select a field containing Numeric 4 and compared with a
> char(30)
> field.
> In oracle and postgresql to version 8.2 worked perfectly, now the new
> version no longer works, as we have many queries in this format.
Hard to say without havi
On Fri, 2009-10-02 at 02:17 +, Dan French wrote:
> #1: bytea_string = '"0"' (table; bytea)
> Function:
>trim('"' both from bytea_string)
> fails and returns: '"0'
Works for me. Please submit a complete test case.
> #2: Come on folks: Bytea is a series of bytes. Conversion to ASCII is
On Fri, 2009-10-09 at 07:51 +, Mohamed Altamimi wrote:
> I am new in Postgres .How i can give relationship between two tables 1 to
> many. I am using pgAdmin III.
This is not a bug. There are other forums for user support.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To
On Mon, 2009-10-12 at 20:42 -0400, Turner, Ian wrote:
> --- postgresql-8.4-8.4.1/src/backend/libpq/auth.c 2009-06-25
> 12:30:08.0 +0100
> +++ postgresql-8.4-8.4.1-fixed/src/backend/libpq/auth.c 2009-09-15
> 20:27:01.0 +0100
> @@ -166,6 +166,8 @@
> #endif
>
> static int
On Mon, 2009-10-19 at 11:05 +, Roman Kapusta wrote:
> I have table with bytea column, which is indexed (1)
> I want to use index during pattern matching (eg. dir like
> someDirectoryName
> || '/%'), but concatenation of two strings cause error (2)
> So I have to use function convert_to (convert
On lör, 2009-10-24 at 14:01 +, Timothy Madden wrote:
> Can the string literal syntax for CREATE FUNCTION please, please be dropped
> ... ?
>
> http://www.postgresql.org/docs/8.4/interactive/plpgsql-structure.html
>
> It is not ANSI/ISO and so annoying for compatibility.
Whatever is inside th
The following bug has been logged online:
Bug reference: 5137
Logged by: Peter Bengtson
Email address: pe...@peterbengtson.com
PostgreSQL version: 8.3.8
Operating system: Debian, Mac OS X
Description:Upgrade policy clarification
Details:
It would be good if you to
On sön, 2009-10-25 at 13:52 +, Peter Bengtson wrote:
> It would be good if you to the page describing how a db dump is required
> only for major verson upgrades, e.g. from 8.3.x to 8.4.x but not from, say,
> 8.3.7 to 8.3.8, could add a proviso: a DB dump *is* necessary when upgrading
On fre, 2009-11-06 at 17:29 +, Jason wrote:
> When I have a plpythonu function returning a composite type that has an
> array column, the function does not work when I try to return a list for
> that column.
There is a patch proposed to address that in 8.5, but before that,
arrays are pretty m
On Sun, 2009-11-08 at 16:33 -0500, Robert Haas wrote:
> On Sat, Nov 7, 2009 at 5:23 AM, Peter Eisentraut wrote:
> > On fre, 2009-11-06 at 17:29 +, Jason wrote:
> >> When I have a plpythonu function returning a composite type that has an
> >> array column, the functi
On tis, 2009-11-10 at 20:45 +, Boh Yap wrote:
> make check
> failed, when trying to initdb, with this message in log:
>
> could not determine encoding for locale "en_AU.US-ASCII": codeset is
> "US-ASCII"
Try using a different locale.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@
On tis, 2009-11-10 at 17:15 -0500, Tom Lane wrote:
> I was wondering what we ought to do about this. I can't find any clear
> documentation about these locales on my Mac, but it sure looks like they
> are effectively encoding-agnostic, which means that it might be
> reasonable to default to SQL_AS
On ons, 2009-11-11 at 14:27 -0500, Tom Lane wrote:
> Okay. Then we need to fix pg_get_encoding_from_locale to distinguish
> "I don't know the locale's encoding" from "I know the encoding and
> it's
> SQL_ASCII". I'm inclined to make it return -1 for the former,
Makes sense.
The other alternativ
On lör, 2009-11-07 at 12:23 +0200, Peter Eisentraut wrote:
> On fre, 2009-11-06 at 17:29 +, Jason wrote:
> > When I have a plpythonu function returning a composite type that has an
> > array column, the function does not work when I try to return a list for
> > that co
The following bug has been logged online:
Bug reference: 5188
Logged by: Peter Dobos
Email address: dvc1...@gmail.com
PostgreSQL version: 8.3.8
Operating system: Win XP
Description:Inheritance: bug or feature?
Details:
Hi,
I'm not sure that inherited table re
On ons, 2009-09-23 at 20:31 -0300, Euler Taveira de Oliveira wrote:
> Marek Lewczuk escreveu:
> > Please execute following example:
> > select * from ts_debug('english', ' > align="right" style="margin: 0px 0px 5px 5px;" test_aa="26461"/>')
> >
> > As the result you will see, that is not identifi
On mån, 2009-11-16 at 10:19 +0100, Pavel Stehule wrote:
> wrong:
>
> pa...@nemesis ~]$ psql postgres -v x=10 -c "select :x"
> ERROR: syntax error at or near ":"
> LINE 1: select :x
>^
This is documented in the psql man page.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@pos
On mån, 2009-11-16 at 12:28 +0100, Pavel Stehule wrote:
> 2009/11/16 Peter Eisentraut :
> > On mån, 2009-11-16 at 10:19 +0100, Pavel Stehule wrote:
> >> wrong:
> >>
> >> pa...@nemesis ~]$ psql postgres -v x=10 -c "select :x"
> >> ERR
On tor, 2009-11-26 at 22:59 -0500, Robert Haas wrote:
> ISTM that if you run psql with "-f -", you shouldn't expect to get an
> interactive shell. Rather, you should expect psql to do whatever it
> normally does when given -f somefilename, except using stdin rather
> than the file. After all, you
On tor, 2009-12-03 at 14:46 -0800, David Gardner wrote:
> Not sure about the try block being related, I included it in my
> example mostly because the example is a simplified version of some
> code I was working on that had a try/except block.
> I tried the function without the try block and it ra
On tor, 2009-12-03 at 19:02 -0500, Tom Lane wrote:
> Peter Eisentraut writes:
> > ... So you should not try to assign to
> > the parameters of a function.
>
> If it's allowed in normal Python functions, that definitely needs to be
> documented. Better would be to fi
On mån, 2010-01-04 at 03:48 +, Ben Woosley wrote:
> However, unique and foreign key constraints added using the "alter
> table add
> constraint" syntax fail on the column name. At this point the
> statement has
> enough information (the host table name) to properly identify the
> column
> desp
On tor, 2010-03-04 at 07:31 +, Alexender wrote:
> This is real problem.
> Dump from Postgres 8.2 can't be restored in Postgres 8.4
> if I use on server 8.2 encodings KOI8 and --lc-collate and --lc-ctype
> uk_UA.KOI8-U
> Because conversion is not supported between KOI8R and KOI8U and
> dump 8.
On ons, 2010-02-24 at 12:16 -0500, Tom Lane wrote:
> Joe Conway writes:
> > Related to this I have noticed in recent weeks on my own development
> > machine that "make install" takes *much* longer, but only sporadically,
> > due to the docs building.
>
> This might be related to Peter's changes t
On tor, 2010-03-04 at 12:09 -0500, Robert Haas wrote:
> I think that the whole idea of make targets building different things
> depending on what you've built previously is confusing,
> counterintuitive, and illogical. make all should either build the
> docs, or not; trying to guess what the user
On tor, 2010-03-04 at 17:53 +, Lou Picciano wrote:
> While I'd agree a 'make all' should, uh... make _all_, and that make
> building based on lots of guessing is counterintuitive, an option to
> configure like:
>
> ./configure --no-docs or ./configure --with-htmldocs-only
>
> - with som
On fre, 2010-03-05 at 08:09 -0500, Tom Lane wrote:
> Peter Eisentraut writes:
> > On tor, 2010-03-04 at 17:53 +, Lou Picciano wrote:
> >> ./configure --no-docs or ./configure --with-htmldocs-only
>
> > But that would be a negative regression for end users, who w
On mån, 2010-03-15 at 14:13 -0700, Josh Berkus wrote:
> 1. Create a function.
> 2. In one session, start an explicit transaction.
> 3. Do a CREATE OR REPLACE on the same function, but do not commit.
> 4. Open a 2nd session, and an explicit transaction in that session.
> 5. Do a CREATE OR REPLACE on
On sön, 2010-01-31 at 13:20 +0100, Steve White wrote:
> Robert suggested that I start some documentation about limitations of
> PL/Python. Find attached.
>
> I think it would also be good to explain the meaning of "trusted" regarding
> PL/Python, and how it might impact the user. There is alread
The following bug has been logged online:
Bug reference: 5398
Logged by: Peter Jukel
Email address: pju...@triplehash.com
PostgreSQL version: 8.4
Operating system: Mac OSX 10.5.8
Description:psql gives syntax error on .sql files with UTF-8 BOM
Details:
The psql
On sön, 2010-04-18 at 13:12 -0400, Robert Haas wrote:
> That all sounds pretty reasonable to me, though I would favor using
> something other than Bugzilla for the tracker. I'm not really sure if
> there's anything that I'd consider truly good out there,
There isn't. Welcome to the show.
;-)
On sön, 2010-04-18 at 19:47 +, Greg Sabino Mullane wrote:
> > That all sounds pretty reasonable to me, though I would favor using
> > something other than Bugzilla for the tracker. I'm not really sure if
> > there's anything that I'd consider truly good out there, but I've
> > always found Bug
On mån, 2010-04-19 at 09:59 +0200, Stefan Kaltenbrunner wrote:
> I think we would not even need to expose the webinterface to the wider
> community, what we probably want is something that let's us keep the
> current workflow but provides a minimalistic
> status/statistics/dashboard
> feature on
On mån, 2010-04-19 at 15:37 -0400, Robert Haas wrote:
> As far as I am concerned, this is just bellyaching. I'm glad Tom
> fixes most of the bugs because otherwise we would have a lot more
> unfixed bugs. But he's not from the only one who responds to bug
> reports, and we seem to have a pretty g
On fre, 2010-04-30 at 12:55 +0200, Martin Pitt wrote:
> Hello PostgreSQL developers,
>
> 9.0beta5 seems to enable -Werror by default (which is a good thing,
> thanks!).
You probably mean alpha5, unless you come from the future. ;-) That was
actually a mistake in the packaging, which is why there
On fre, 2010-04-30 at 14:43 +0200, Andres Freund wrote:
> On Friday 30 April 2010 13:56:11 Peter Eisentraut wrote:
> >
> > You probably mean alpha5, unless you come from the future. ;-) That was
> > actually a mistake in the packaging, which is why there is a -revised
On fre, 2010-04-30 at 03:51 +, Claudio wrote:
> The following bug has been logged online:
>
> Bug reference: 5443
> Logged by: Claudio
> Email address: clau...@livra.com
> PostgreSQL version: 8.3.7
> Operating system: CentOS
> Description:Undetected deadlock situat
H build starting from a
> distribution tarball. The OP is correct that things are going to fall
> over in that case. My thought about fixing it was that postgres.bki
> and related files ought to be forced to be built/used in $(srcdir),
> but I didn't get further than that. Peter,
On sön, 2010-05-09 at 11:35 -0400, Tom Lane wrote:
> bry...@giraffe-data.com (Bryan Henderson) writes:
> > The interface header files for Postgres server extensions define "bool",
> > but that name is commonly used by other parts of user code, including
> > by standards (C99, C++). That causes, at
On sön, 2010-05-09 at 17:37 +, Bryan Henderson wrote:
> >it would be
> >better if Bryan could show us a concrete example that is causing
> >problems.
>
> I don't know how concrete you want.
Something one can download and compile.
> A user defined function server extension
> #includes a heade
On mån, 2010-05-10 at 02:02 +0100, Greg Stark wrote:
> I don't see any other conflicts offhand that would create problems
> using a c99 compiler to build server modules. It's quite annoying and
> sad that they added "bool" to c99 since otherwise it would just be a
> drop-in replacement with extra f
On mån, 2010-05-10 at 15:55 +, Bryan Henderson wrote:
> >>> I don't know how concrete you want.
> >
> >Something one can download and compile.
>
> That wouldn't be worth anyone's effort, since the problem is esaily
> enough elucidated with a few words of explanation. I.e. I'm sure you
> can i
On tis, 2010-05-11 at 14:42 -0400, Robert Haas wrote:
> I guess the question that comes to mind for me is how many other
> things fall into this category. We define a lot of symbols like int4
> and int32 that other people could also have defined, and I don't
> really want to s/^/pg/ all of them.
On ons, 2010-05-12 at 12:44 +0100, Greg Stark wrote:
> Well you could imagine doing this for all our types by doing:
>
> search and replace int4 -> pgint4 etc.
> add #ifndef int4 #define int4 pgint4 at the end of postgres.h
>
> That way third-party apps which define their own int4 would be
> requ
On tis, 2010-05-04 at 22:46 +0300, Peter Eisentraut wrote:
> On tis, 2010-05-04 at 10:49 -0400, Tom Lane wrote:
> > Alvaro Herrera writes:
> > > Graham wrote:
> > >> Build with VPATH works well upto installing
> > >> postgresql-9.0beta1/src/backend/c
On mån, 2010-05-17 at 16:43 +0800, 毅 黄 wrote:
> [r...@centos-jht postgresql-8.4.1]# ./configure
> --prefix=/home/eps/pgsql-8.4 --host=arm-linux --without-readline
> --disable-spinlocks --enable-depend
> --without-zlib CC="/usr/local/arm/4.3.2/bin/arm-linux-gcc"
> [r...@centos-jht postgresql-8.4.1
Kardos, Dr. Andreas writes:
> I have tested the pg_dumpall (with PATHNAME stuff) which Peter E. has mailed
> to this list.
>
> It works fine on QNX4 but definitly not on Digital Unix.
>
> The version in CVS works in general, but not on QNX4. On QNX4 I have to
> remove t
e, what is the name, what is the filesystem layout, etc.? Details.
FWIW, all of "-f", "<", and "\i" work for me. It would be noticed pretty
quickly if those failed in general.
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED]
Cary O'Brien writes:
> Executing a "select ... for update" corrupts index files.
I can confirm that in 6.5.2. *shudder* But 7.0.0 looks fine.
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
htt
POSTGRESQL BUG REPORT TEMPLATE
Your name : Peter Hunter
Your email address : [EMAIL
rent scheme of potentially many
superusers perfectly lends itself to the "I do everything as root" abuse
and is also very vulnerable because one superuser can easily revoke
superuser privilege from all the others.)
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
unsigned
with zero stem mostly from the fact that you can't assume that size_t is
unsigned on all platforms.
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
7;m just a
pedestrian though, does anyone know what it is supposed to be for?)
That sure sounds like Perl once again trying to circumvent the autoconf
logic.
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
t every GCC on every Alpha now and in the future
will have it? What does "doesn't appear to handle properly" mean anyway?
Have you notified the GCC maintainers?
Also, whose idea was it to use '__inline__' instead of 'inline'?
--
Peter Eisen
Jan Wieck writes:
> Peter, you said you'll probably work on the ACL stuff after 7.0. We
> need to coordinate that work with the function manager redesign to go
> for SETUID triggers and functions.
Yes, very nice feature. Far down the road in my dreams though. However,
SQL ha
tember! The system is pretty smart. Of course after 2037 we're
doomed anyway.
The bottom line is that INTERVAL in its current implementation has
deficiencies and it's not SQL compliant either.
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
id,it.el_id,ip.ip_id,m.c_id,m.ip_id
> from ip_categories cat, ip_cat_items it, ip_cat_map m, ip_item ip,
> fund_class f
> where cat.cat_table='fund_class' and cat.cat_id=it.cat_id and
> it.el_id=f.fc_id and m.c_id=it.c_id and m.ip_
> Bruce had actually put in some code to emit warnings, but Thomas
> objected to it for reasons I don't recall clearly.
I think it was along the lines of "it's not the backend's task to teach
SQL". Incidentally, it could be, with the SQL flagger (sec. 4.34).
--
Pete
t for now you're stuck with it.
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
e error at or near """
The password must be single-quoted nowadays. Put that on the 7.0.1 list
...
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
rlying syntax is really
> CREATE USER WITH PASSWORD
Yes, that's why we made that change. I was more referring to the pgaccess
"list". Sorry.
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
| table|
| pgsql | company_pkey| index|
| pgsql | marketplace | table|
| pgsql | marketplace_pkey| index|
| pgsql | news| table|
| pgsql | news_pkey | index|
| peter | productcatego
er,password)!=""} {
! set cmd "$cmd WITH PASSWORD '$PgAcVar(user,password)' "
}
set cmd "$cmd $PgAcVar(user,createdb) $PgAcVar(user,createuser)"
if {$PgAcVar(user,validuntil)!=""} {
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
27;m hoping to get the --program-suffix like configure options
working, so the current scheme is going to blow up anyway. Something to
think about maybe.
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
Rainer Tammer writes:
> The regression test fails on a couple of topics.
> -> HINT --enable-locale !!
You need to unset all your locale settings before running the
tests. (any or all of LC_*, LOCALE, LANG, LANGUAGES, etc.)
--
Peter Eisentraut Sernanders väg 10:1
egmentation fault or
failed assertion in the backend involved, which we'd need to see.
> !# \d
> You are currently not connected to a database.
> !# \c can
> No Postgres username specified in startup packet.
> Segmentation fault
That's certainly a psql problem. Can
uot; is not
> used at all.
Sure it's used. Just because it's not mentioned in the select list doesn't
mean it will be ignored completely. What you get here is a three-way join,
which is of course slower than a two way join.
--
Peter Eisentraut Sernanders väg 10:1
two
bugs in the CIDR input routine:
1) '10.8.7.6/16' in not rejected
2) Since it is accepted, at least the hidden fields need to be zeroed.
(But note that this bug is only exposed when you use the type improperly
in the first place.)
Using the same operators for
might be worth hard-coding a few popular
ones.
> I'm also wondering if the left-hand inequality ('foo' <= any string
> beginning with 'foo') might fail in some locales ... we haven't seen
> it reported but who knows ...
I think that's pretty saf
to merge the changes back into Byrons stuff but that has not
happened (that I am aware of).
It would be great if this driver could be common and even better if any common
driver was to be based upon unixODBC (i.e. its odbcinst etc).
Peter
NOTE: There is no reason, that I am aware of, why a common
Well the driver is derived from the MS Windows driver (Byrons) so it has to
adhere to whatever licensing that is there but unixODBC is, in general, LGPL.
Peter
On Thu, 15 Jun 2000, Lamar Owen wrote:
> Peter Harvey wrote:
> >
> > The PostgreSQL driver, in unixODBC, is a direc
O format, since the ISO format is
fixed.
> P.S.: Is there a way to change the Datestyle to Postgres without a
> SQL-Statement, e.g. ENV-Variable or config-file?
PGDATESTYLE environment variable. Config file I'm working on.
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
> switch01.tor | 1 | 127.0.0.2 | 255.0.0.0
> switch01.tor | 2 | 127.0.0.3 | 255.0.0.0
> switch01.tor | 3 | 209.250.155.8 | 255.255.255.224
> (2 rows)
>
>
> 127.0.0.2 | 255.0.0.0 and 127.0.0.3 | 255.0.0.0 - it's
to end a command issued to
> "psql" starting with a backslash "\" with a semicolon ";", eg.
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
not to decide that.
--
Peter Eisentraut Sernanders väg 10:115
[EMAIL PROTECTED] 75262 Uppsala
http://yi.org/peter-e/Sweden
s in the specified family cannot be used with this socket
Try `createuser -h localhost ...'. By default, it uses Unix domain
sockets, which don't work on NT. (Hence, "specified family [namely
AF_UNIX] cannot be used...".)
Setting the environment variable PGHOST=localhost mi
write the output to a text file I can create lines much longer than
256 characters, which seems to support that claim of blame.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
ply the attached patch.
You need to restart the server to get it to load the new object file.
Also note that there is a disagreement among experts over one particular
part of the algorithm. Check it out with your favourite search engine.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.
Bruce Momjian writes:
> OK, this was a good point. Were did we leave this, folks?
I was going to do some extensive work on the privilege system, but if you
guys always postpone beta for a month just a day before it was supposed to
be I'll never know when to start.
--
Peter Ei
case CMD_DELETE:
> > + reqperm = ACL_DE;
> > + break;
> > + case CMD_UPDATE:
> > +
ce does include the
correct 6.5.3 source (it didn't get released with 6.5.3 due to me messing
up the cvs commit :-( )
> PLEASE POSTGRESQL PEOPLE I NEED AN ANSWER!!! I COULD LOOSE MY
> JOB OVER THIS.
Also, you are using transactions (see the setAutoCommit(false) above)?
Peter
--
Peter T Mount
the current shell.
$ sh
$ echo $FOO # The $FOO is expanded by the subshell.
So, to pass a tab via the psql command line, you have to convince your
shell to do it.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
INSERT INTO
::=
::=
|
|
::=
[]
[ ]
::=
::=
[ { }... ]
::=
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
e from t1 where f1=1;
> ERROR: triggered data change violation on relation "t1"
You cannot change data twice within a transaction if there's a RI
constraint on the table. This is per SQL, nothing we can do about it.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
it's too boring to quote...)
Note that it talks about "statements", not "transactions".
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Bruce Momjian writes:
> Unfortunately, I can't reproduce the problem in the current source tree.
I fixed it.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Why JDBC Driver returns column (procedures etc.) name pattern in lower case?
JDBC doesn't change any case, so unless you quoted the column when the
table was created, it will return it in lower case because the backend has
done the deed.
Peter
--
Peter T Mount [EMAIL PROTECTED] http://www.rete
to be used in
unaligned output mode. That way one can cre
ate, for example, tab- or comma-separated
output, which other programs might prefer.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
daryl lamble writes:
> Just to let you know it looks like ver 7.0 does not run on SuSE7.0 SMP
> Kernel.
Could you be more specific than "looks like does not run"?
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
101 - 200 of 900 matches
Mail list logo
