The following bug has been logged online:
Bug reference: 2995
Logged by: Bruno
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Windows XP SP2
Description:PSQLRestore crash and MemoryLeaks!
Details:
Hello,
We see many memory leaks using
The following bug has been logged online:
Bug reference: 3111
Logged by: Bruno
Email address: [EMAIL PROTECTED]
PostgreSQL version: v8.2.3
Operating system: Win2003 Server 64bits
Description:PostgreSQL Driver is compatible with Win2003 Server 64
bits?
Details
The following bug has been logged online:
Bug reference: 4583
Logged by: Bruno Pimenta
Email address: brunofpime...@gmail.com
PostgreSQL version: 8.1.4
Operating system: Windows 2003 Server SP2
Description:Db stop
Details:
I have a system in Java and I'm usin
Your name : Pinaud Bruno
Your email address : [EMAIL PROTECTED] or [EMAIL PROTECTED]
System Configuration
-
Architecture : Pentium 3
Operating System : RedHat Linux 6.1
PostgreSQL version : PostgreSQL-7.0 Beta1
The following bug has been logged online:
Bug reference: 2497
Logged by: bruno Corbin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: linux
Description:bug initdb
Details:
copying template1 to postgres ... FATAL: could not create file
Helo
I have a problem with postgres_beta4.
I wanna know as resolv this problem.
I'm using Windows Server 2003.
Thank You,
Bruno Necchi.
error:
C:\winpsql\bin>createuser
Enter name of user to add: e
Shall the new user be allowed to create databases? (y/n) y
Shall the new
Hi,I'm using postgres version 7.4.5
and had a problem with interval
Here is my query :
select '2004/10/31'::timestamptz + '1
day'::interval;
Here is the answer :
10/31/2004 11:00:00 PM
Is it a bug or I do something wrong?
I tested my query on 3 server and have always the same
answer.
The following bug has been logged online:
Bug reference: 4944
Logged by: Bruno Scovoli Santos
Email address: bruno.scov...@gmail.com
PostgreSQL version: 8.3.7
Operating system: Ubuntu 9.04 Jaunty Jackalope
Description:Problems with using \set variables as strings in
POSTGRESQL BUG REPORT TEMPLATE
Your name : Bruno Wolff III
Your email address : [EMAIL
I think the problem is somehow related to roman numeral conversion when
some values are null.
The following seems to work:
select case when gen is not null then to_char(gen,'rn') else null end, case when gen
is not null then to_char(gen+1,'rn') else null end from cname;
While the following doesn'
POSTGRESQL BUG REPORT TEMPLATE
Your name : Bruno Wolff III
Your email address
ug report. Can you report
> simple data select (how data go into your query - for example same query
> but without to_char())?
>
> Thanks.
> Karel
>
>
> > >
> > > Here is a sample of one kind of error I was getting with the about query
I was moving a small database I had from 7.0.3 to 7.1beta3 using pgdump
and had a problem with a view. The I got a syntax error when the rule
corresponding to the view was being processed. While looking around I
noticed that the dump file created a table with the name of the view
instead of creati
A problem I reported a few weeks ago here using to_char to do a conversion
to roman numerals with many of the values being null doesn't seem to be
a problem in 7.1beta3.
The query below used to work with 7.0.3. If I change 'lower(title)' to
'title' in the order by clause, then the query is accepted.
area=> select code, wbc.gameid, title from games, wbc where wbc.gameid = games.gameid
union select code, null, null as title from wbc where gameid is null order by c
On Wed, Jan 24, 2001 at 05:50:24PM -0300,
Gonzalo Arana <[EMAIL PROTECTED]> wrote:
>
> It seems that there is a problem when retrieving a timestamp value (rounding).
>
> NO minute has 61 seconds. Am I wrong?
When leap seconds occur, minutes can have 61 seconds.
Are you running version 7.1 or higher?
On Tue, Aug 21, 2001 at 09:25:58AM -0400,
[EMAIL PROTECTED] wrote:
> Martijn Beelen ([EMAIL PROTECTED]) reports a bug with a severity of 2
>
> Long Description
> When using left join, I get the errormessage
> "ERROR: OUTER JOIN is not yet supported"
patch
to how foreign keys are checked. The machines where both running
Redhat linux 6.1 with a 2.2.16 kernel.
Below is a sample psql session that I think illustrates the problem.
Script started on Wed Jan 9 11:17:06 2002
[bruno@wolff bruno]$ psql
Welcome to psql, the PostgreSQL interactive te
Please don't use the bug reporting facilities to ask support questions.
pgsql-general@postgresql.org would be a reasonable list to ask your question.
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives
Please don't use the bug reporting facilities to ask support questions.
Your question would be appropiate for either the pgsql-general@postgresql.org
or [EMAIL PROTECTED] mailing lists.
---(end of broadcast)---
TIP 1: if posting/reading through Usene
On Fri, Jul 21, 2006 at 07:41:02 +,
Alaa El Gohary <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
The report below isn't a bug, its a performance question and should have
been sent to [EMAIL PROTECTED] I am redirecting replies there.
> A query on the postgresql DB
On Wed, Aug 30, 2006 at 10:18:46 +0200,
Filip Hrbek <[EMAIL PROTECTED]> wrote:
>
> It is possible that the corruption was caused by a HW problem at customer's
> server, and then this problem appeared also at our development environment
> because of the data already beeing corrupted. I will rec
On Mon, Sep 25, 2006 at 14:59:46 +0200,
Harald Armin Massa <[EMAIL PROTECTED]> wrote:
> Asaf,
>
> SQL-92 states that identifiers [for dictionary objects] are limited to 128
> characters and are case-insensitive (unless delimited by double quotes),
> because they are automatically translated into
This shouldn't have been submitted to the bugs list, as it isn't a bug.
The best spot for this kind of question is the performance list so I am
copying it there and redirecting followups there.
On Wed, Sep 27, 2006 at 20:56:32 +,
Graham Davis <[EMAIL PROTECTED]> wrote:
>
> SELECT assetid, m
On Fri, Nov 03, 2006 at 09:50:01 -0200,
Marcio <[EMAIL PROTECTED]> wrote:
> I have a sugestion for pgsql 8.2 or next versions ...
> Is complicated encrypt the procedures/functions on Database like Oracle or
> similar?
> I sugest this because we develop ERP/MRP with complex routines and we like
>
This isn't a bug and you should have asked on a different list. I am going
to move this over to pgsql-general.
On Mon, Nov 20, 2006 at 12:07:25 +,
"S.Balaji" <[EMAIL PROTECTED]> wrote:
>
> In Redhat 7.2 use Pg; command in perl Scripts will working with out any
> Problem.But in CentOS use Pg
This really should have been asked on pgsql-performance and would probably
get a better response there..
On Sun, Nov 26, 2006 at 16:35:52 +,
Michael Simms <[EMAIL PROTECTED]> wrote:
> PostgreSQL version: 8.1.4
> Operating system: Linux kernel 2.6.12
> Description:Performance seriou
On Tue, Nov 28, 2006 at 00:21:27 +,
Lucian Capdefier <[EMAIL PROTECTED]> wrote:
>
> 1. I cannot user table alias in the FROM clause of the DELETE statement.
That isn't in the SQL spec, but the extension to allow it has been added
to 8.2 which will be released very shortly.
> 2. I cannot us
On Fri, Dec 01, 2006 at 20:41:32 +,
Albert Strasheim <[EMAIL PROTECTED]> wrote:
>
> Description:Feature request: tinyint and unsigned types
You can already use "char" to store 1 byte values, though unless there are
several of these in a row, you won't save any space because of align
This should have been asked on the performance list, not filed as a bug.
I doubt anyone will have a complete answer to your question without
EXPLAIN ANALYZE output from the query.
Have you ANALYZE'd the tables recently? Poor statistics is one possible
cause of the issue you are having.
On Fri, Ma
On Thu, Jun 20, 2002 at 17:28:31 +0200,
Ingo Ciechowski <[EMAIL PROTECTED]> wrote:
> Hi,
>
> first of all let me tell all of you that PostgreSQL is among the best
> in OpenSource!
>
> Unfortunaly there's a (hopefully easy to fix) bug in release 7.2 and
> 7.2.1 that was not there in 7.1.3 and
In cube_out 100 bytes are allocated to hold the output string. Instead
using a bound on the size of g format output and separation characters,
this bound times twice the dimension (possibly plus a small constant for
parens and terminating 0 byte) should be used.
With this approach you might want
When trying to build from CVS, interfaces/perl5 doesn't build unless I add
an include of "c.h" in Pg.c.
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMA
The lex scanner for the cube package has an apparent error in its
pattern for matching floating point numbers. It doesn't except cases
where there is no digit between a sign and a decimal point. For example
-.1 is not matched by the pattern.
I have attached a patch to cubeparse.l and the regressi
In the function cube_yyerror an output buffer of 256 bytes is allocated
to be used for an error message that outputs some of the input buffer.
I think the portion of the input buffer that is echod can potentially
be longer than this.
---(end of broadcast)--
On Mon, Aug 26, 2002 at 00:34:00 -0400,
Tom Lane <[EMAIL PROTECTED]> wrote:
> Bruno Wolff III <[EMAIL PROTECTED]> writes:
> > When trying to build from CVS, interfaces/perl5 doesn't build unless I add
> > an include of "c.h" in Pg.c.
>
> Works
In the section on mathematical functions the following is given for atan2:
atan2(x, y) inverse tangent of a/x
I believe the correct version should either be:
atan2(y, x) inverse tangent of y/x
or
atan2(x, y) inverse tangent of x/y
I beleive the documentation was also wrong for 7.2 where it was:
On Fri, Oct 18, 2002 at 07:23:29 -0400,
[EMAIL PROTECTED] wrote:
> Bhuvan A ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> now() in transaction
>
> Long Description
> I am using 7.2.1. now() returns same value ever, w
On Sat, Nov 16, 2002 at 15:18:58 -0500,
Tom Lane <[EMAIL PROTECTED]> wrote:
> Neil Conway <[EMAIL PROTECTED]> writes:
> > Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> "Random" randomly fails. It is OK.
>
> > So why is it a regression test, then?
>
> It's hard to see how you could test random
not in the middle of a large transaction.
bruno=> create table test (col1 timestamp);
CREATE TABLE
bruno=> copy test from stdin;
Enter data to be copied followed by a newline.
End with a backslash and a period on a line by itself.
>> 11/31/02
>> \.
ERROR: copy: line 1, Bad
On Wed, Dec 18, 2002 at 09:14:18 -0600,
Bruno Wolff III <[EMAIL PROTECTED]> wrote:
> It looks like when a bad date is entered using COPY the backend connection
> gets killed.
I just tried it with 7.3.1 and get the same error.
---(end
On Mon, Jan 27, 2003 at 21:53:27 +0100,
[EMAIL PROTECTED] wrote:
> hi,
>
> last year (2002) the date december 31st is in week 1 of 2003.
>
> it is not possible to get this out of a date-column using EXTRACT or
> to_char.
> to_char( '2002-12-31', 'WW' ) returns 1, and
> to_cha
On Tue, Feb 11, 2003 at 00:13:44 +0200,
Elias Athanasopoulos <[EMAIL PROTECTED]> wrote:
>
> And my GNU bison is version 1.28.
>
> I'll maybe have to upgrade. Thanx for your answer.
I think you need to upgrade to at least 1.75.
---(end of broadcast)-
On Tue, Mar 11, 2003 at 15:42:41 +0700,
Ruslan A Dautkhanov <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> Just a little simple example:
>
> isbs=# \d radauth
>Table "public.radauth"
> Column |Type | Modifiers
> --+
A typo in src/backend/libpq/hba.c breaks local ident authentication
in the SO_PEERCRED case. elif is misspelled as elsif for the test.
A patch is attached.
*** hba.c Sat Mar 15 10:15:46 2003
--- hba.c.old Sat Mar 15 10:15:29 2003
***
*** 1248,1254
return true;
On Fri, Mar 21, 2003 at 16:44:07 +0530,
DEEPANSHU GARG <[EMAIL PROTECTED]> wrote:
> Hi,
> We have a problem when logging in postgresql.
> We are setting the user id and password using Create User command.
> Now when we login the postgresql using
> $psql -U username databasename
> it does'nt prom
On Sat, May 31, 2003 at 00:14:18 -0600,
Dave E Martin XXIII <[EMAIL PROTECTED]> wrote:
> version: 7.3.2
>
> Currently this table has one row in it, where name is 15 unicode
> characters long. It would seem that there would be no need for an index
> on name. However, doing:
It probably has one
On Fri, May 30, 2003 at 16:33:55 +0400,
Nick Altmann <[EMAIL PROTECTED]> wrote:
> Hello!
>
> I think it's not bug, but difficulty.
>
> I cannot use trusted connections for my localhost. I use password. But psql,
> pg_dump, pg_restore doesn't support password parameter in command line. Also, i
On Sat, May 31, 2003 at 16:56:56 -0600,
Dave E Martin XXIII <[EMAIL PROTECTED]> wrote:
>
> (ok, experimented a bit more just now)
> Hm, it appears that degredation occurs with the index as well, I guess
> at the time I created the index, it just initially did better because it
> got to skip al
On Sat, May 31, 2003 at 17:17:38 -0600,
Dave E Martin XXIII <[EMAIL PROTECTED]> wrote:
> Speaking of which, since the row is locked with select for update (so it
> can't be involved in any other transactions anyway) and the change
> doesn't change the length of the row, can't it just be updated
h pg_dump (with 7.3.x), but don't
know for sure. It should be easy for you to try this yourself.
>
> - Original Message -
> From: "Bruno Wolff III" <[EMAIL PROTECTED]>
> To: "Nick Altmann" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]&
On Sun, Jun 01, 2003 at 01:20:03 -0600,
Dave E Martin XXIII <[EMAIL PROTECTED]> wrote:
> Rod Taylor wrote:
>
> >An 8 k page will hold approx 140 tuples based on your structure. So,
> >for every ~100 updates you'll want to run vacuum (regular, not full) on
> >the table
>
> Alas, for this applica
On Tue, Jul 29, 2003 at 09:48:37 -0600,
"Valsecchi, Patrick" <[EMAIL PROTECTED]> wrote:
>
> When doing the following query, it's obvious that postgres should use
> the index:
>
> stats=# explain select min(time) from call;
This has been discussed on the mailing lists numerous times. If you are
On Tue, Aug 19, 2003 at 21:24:50 +0800,
Chris M <[EMAIL PROTECTED]> wrote:
> I also find something magic when using sequence.
> select nextval('seq_test');
> and
> select nextval('"seq_test"');
> both refer to the same sequence: seq_test.
>
> If I want to use a sequence with name: SEQ_TE
On Wed, Aug 27, 2003 at 15:50:32 +0300,
Tarhon-Onu Victor <[EMAIL PROTECTED]> wrote:
>
> The problems is that only ~15% of the lines are inserted into
> the database. The same script modified to insert the same data in a
> similar table created in a MySQL database inserts 100%.
Did you
On Wed, Sep 03, 2003 at 23:19:24 -0700,
Ringo <[EMAIL PROTECTED]> wrote:
> What a prick..
>From observing Tom's responses here, I think this is a real question (not
an RTFM response). If the documentation doesn't make it clear to new readers
that explain analyze does execute the query (though do
On Wed, Oct 01, 2003 at 10:26:57 -0700,
Theodore Petrosky <[EMAIL PROTECTED]> wrote:
> I am not sure but i thought I read something of this
> problem and maybe its not a problem but my
> understanding.
>
> There are only 30 days in september however I can not
> seem to make a query that asks for
On Mon, Nov 10, 2003 at 21:48:30 +0100,
Gaetano Mendola <[EMAIL PROTECTED]> wrote:
> Seems to me too, from the standard:
>
> "The order of execution of a set of triggers is ascending by value of
> their timestamp of creation in their
> descriptors, such that the oldest trigger executes first. I
On Fri, Dec 05, 2003 at 12:47:58 -0400,
PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote:
>
> All is well with psql authentication. However, when I tried to
> use knoda/hk_classes to access the database, I could not get authenticated. A
> typical error message was IDENT authentication failed fo
On Tue, Dec 30, 2003 at 19:32:03 +0530,
Sh A Guru Prasad <[EMAIL PROTECTED]> wrote:
>
> Hi, How to convert number format (with decimal) into
> integer only ex:to conver 100.00 to 100.
Depending on what kind of rounding you want, you can just cast to
an integer. You could also use ceil, floor o
On Thu, Feb 12, 2004 at 12:46:27 -0600,
Javier Carlos <[EMAIL PROTECTED]> wrote:
>
> bd_temporal=> SELECT * FROM tbl_temp WHERE var < 0.20;
> var
> --
> 0.1
> 0.11
> (2 rows)
> bd_temporal=> SELECT * FROM tbl_tem
On Thu, Feb 19, 2004 at 16:52:37 -0800,
Wade Klaver <[EMAIL PROTECTED]> wrote:
> Hello folks.
>
> I just noticed some funky behaviour on the part of date_part. If there is
> some reason this is correct behaviour, I wouldn't mind knowing why.
> The problem is that date_part can return different
On Mon, Feb 23, 2004 at 21:26:57 -0400,
PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote:
>
> Details:
>
> === SQL ===
>
> CREATE TEMP TABLE testing (col_a integer, col_b integer);
> CREATE TEMP SEQUENCE seq;
>
> /* this statement will produce the expected result */
> INSERT INTO testing (col_
I am going to try to move this over the sql list, since it doesn't belong
on bugs.
On Tue, Feb 24, 2004 at 23:47:48 +1300,
Martin Langhoff <[EMAIL PROTECTED]> wrote:
> Tom Lane wrote:
>
> >How about
> >
> >SELECT nextval('seq'); -- ignore result
> >
> >INSERT INTO ... VALUES (currval('seq
On Mon, Mar 01, 2004 at 20:28:02 -0500,
Tom Lane <[EMAIL PROTECTED]> wrote:
> Michael Glaesemann <[EMAIL PROTECTED]> writes:
> > In both cases, the CHECK constraint uses a function that is stable or
> > volatile. It was suggested that functions used in CHECK constraints be
> > restricted to imm
On Thu, Mar 04, 2004 at 13:56:42 -0400,
PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
This isn't a bug. Weeks that span years are treated as part of the year
in which Thursday of that week lies.
>
> Bug reference: 1094
> Logged by:
On Thu, Mar 25, 2004 at 12:25:33 +0100,
Martin Pitt <[EMAIL PROTECTED]> wrote:
>
> Either way, this situation leads to a DoS of the database system or the
> entire machine. Since any user with enough privileges to access the
> database can create and execute functions, this raises a slight secu
On Thu, Mar 25, 2004 at 16:08:49 +0100,
Martin Pitt <[EMAIL PROTECTED]> wrote:
> Hi PostgreSQL hackers!
>
> A while ago we received the bug report below against pg_autovacuum.
> Since it runs as a daemon, it should detach from its controlling
> terminal by executing sth like
>
> int nul
On Sat, Mar 27, 2004 at 00:56:47 +0100,
Martin Pitt <[EMAIL PROTECTED]> wrote:
>
> Well, daemons that run for a long time should not log to
> stdout/stderr, but to syslog. Otherwise they clutter up the screen
> randomly or the messages are not seen at all (when you are only
> working under X for
On Sat, Apr 03, 2004 at 13:51:56 -0500,
Gabriel Weinberg <[EMAIL PROTECTED]> wrote:
>
> I have a table with an integer column with about 10M rows in it.
>
> This column has an index (btree).
>
> When I try to select a row using this column with an integer, e.g. select *
> from table where id=4
On Mon, Apr 19, 2004 at 20:16:15 -0300,
PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1139
> Logged by: Emil Tarazi
>
> Email address: [EMAIL PROTECTED]
>
> PostgreSQL version: 7.4
>
> Operating system: L
On Wed, May 26, 2004 at 13:57:37 -0400,
Vic Ricker <[EMAIL PROTECTED]> wrote:
> Hi. I'm using PostgreSQL 7.4.2 under Fedora Core 1.
>
> I have two tables with a single varchar(32) column in each. I'm trying
> to find all the rows from one table that don't exist in the other
> table. The query
On Mon, Jun 14, 2004 at 01:07:09 +0800,
Fehmi Noyan ISI <[EMAIL PROTECTED]> wrote:
>
> I got the error message as expected. Everything is ok.Now, let's create
> another table called "table_2" with an inheritence from "table_1".
>
> But, when I insert a new value into "table_2" with an "id" v
On Tue, Jun 22, 2004 at 06:29:29 -0300,
PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
This isn't really a bug; you should have posted you question to pgsql-novice.
(Followups set to there and to you.)
>
> Bug reference: 1176
> Logged by:
On Thu, Jul 01, 2004 at 16:42:29 -0300,
Roberto João Lopes Garcia <[EMAIL PROTECTED]> wrote:
>
> When I use string concatenator || and there are fields of type date whith NULL values
> the result is an enpty string. Please see example:
This isn't a bug. If either operand of || is NULL, then the
On Fri, Jul 02, 2004 at 04:50:07 -0300,
PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
This doesn't appear to be a bug at this point. It sounds like you have
a self induced performance problem, so I am moving the discussion to
pgsql-performance.
>
On Fri, Jul 02, 2004 at 10:27:35 -0400,
Tom Lane <[EMAIL PROTECTED]> wrote:
>
> IIRC there were objections the last time it was seriously proposed,
> basically of the form "but that will break my application which relies
> on writing so-and-so without a cast". We did get as far as removing all
On Mon, Jul 12, 2004 at 14:47:34 +0200,
Gaetano Mendola <[EMAIL PROTECTED]> wrote:
>
> As someone says NULL = NULL is false
As someone else pointed out, NULL = NULL is NULL which is not TRUE.
---(end of broadcast)---
TIP 8: explain analyze is you
I see the following behaivor on 7.4.3 and 7.4 stable from about a week ago:
bruno=> create table test ();
CREATE TABLE
bruno=> alter table test add constraint test2 check('\\' = '');
ALTER TABLE
bruno=> \d test
Table "public.test"
Column | Type | Modi
On Fri, Jul 16, 2004 at 16:49:25 -0500,
Bruno Wolff III <[EMAIL PROTECTED]> wrote:
> I see the following behaivor on 7.4.3 and 7.4 stable from about a week ago:
> bruno=> create table test ();
> CREATE TABLE
> bruno=> alter table test add constraint test2 check('\\&
On Tue, Sep 14, 2004 at 00:57:07 +0100,
PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote:
>
> Description:Optimization of SELECT for NOT NULL case
>
> Details:
>
> CREATE TABLE x (id int4 NOT NULL);
> Populate table, for instance, 10M rows;
> SELECT count(*) from x WHERE x IS NULL;
> Op
On Wed, Sep 15, 2004 at 23:29:43 +0300,
Alexander Kirpa <[EMAIL PROTECTED]> wrote:
> On 15 Sep 2004, at 12:21, Bruno Wolff III wrote:
>
> Regarding your point of view possible exist reason for remove
> optimization for case like below
> SELECT count(*) from x where id>
On Wed, Nov 17, 2004 at 11:53:10 -0800,
Josh Berkus <[EMAIL PROTECTED]> wrote:
> Karl,
>
> > I don't care that much about the behavior, it's easy enough
> > to delete 'public'. I do think that a note should be
> > made in the administrator manual regards system upgrades
> > where pg_dump(all) s
On Mon, Nov 29, 2004 at 11:37:50 +,
PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1332
> Logged by: Robert Grabowski
>
> Email address: [EMAIL PROTECTED]
>
> PostgreSQL version: 7.4.6
>
> Operating syst
On Sat, Dec 11, 2004 at 03:33:07 +0100,
Stefan de Konink <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a table with some empty colums, if I try to concat my colums to
> eachother something strange happens. Rather empty column B produces
> virtually no output using the || in the select query. But
On Thu, Dec 16, 2004 at 08:16:56 +,
PostgreSQL Bugs List <[EMAIL PROTECTED]> wrote:
>
> I'm sorry, but I didn't found a better place to report that:
>
> There is no information how to specify user's password in pg_dump
> documentation. I have spent half of day searching for that (pg_hba.co
On Thu, Dec 16, 2004 at 20:21:48 +0100,
Piotr Likus <[EMAIL PROTECTED]> wrote:
>
> Yes, maybe it is insecure, but sometimes "quick and dirty" solutions
> are better than no solution at all.
> After all you can add "not recommended" note to this tip.
The official documentation isn't likely to be
On Wed, Jan 12, 2005 at 08:31:09 +,
Holger Klawitt <[EMAIL PROTECTED]> wrote:
>
> There is no (at least no apparent) link
> to the ChangeLog for the most recent version
> of postgres in neither the announcements nor in the
> news nor in the download section (at top level).
>
> I'd think tha
On Tue, Jan 18, 2005 at 09:01:29 +,
andrzej <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1408
> Logged by: andrzej
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.0-rc5
> Operating system: windows XP
> Descript
On Tue, Feb 15, 2005 at 12:38:17 +,
Zoltan Szmutku <[EMAIL PROTECTED]> wrote:
>
> My next commands :
>
> 1.
> CREATE UNIQUE INDEX kod
> ON proba
> USING btree
> (mezo1)
>
> 2.
> CREATE UNIQUE INDEX kod
> ON proba2
> USING btree
> (mezo1)
>
> The second command not success, I
On Tue, Mar 29, 2005 at 03:54:48 +0100,
Olivier Thauvin <[EMAIL PROTECTED]> wrote:
>
> Maybe I will workaround by setting postgres user access as 'trust' for local
> connection only, but I have to reread the doc before :).
Ident is better if you can use domain sockets and the equivalent of
get
On Tue, Apr 05, 2005 at 18:09:25 +0100,
"Marcus v. Scotti" <[EMAIL PROTECTED]> wrote:
>
> Description:Problem with capitalised DB names...
> Details:
>
> When trying to grant database privileges to a group of users there is no way
> to do this if the database name is capitalised (i.e.
On Tue, Apr 05, 2005 at 21:11:12 +0100,
Eric McGough <[EMAIL PROTECTED]> wrote:
>
> COPY my_table FROM STDIN WITH DELIMITER AS '|';
> \N|\N|\N
> \.
COPY doesn't provide a way to use default values for just some rows.
You can get the default for a column by leaving it out of an explicit
column l
On Mon, Apr 11, 2005 at 09:37:08 +0100,
"Marcus v. Scotti" <[EMAIL PROTECTED]> wrote:
>
> Thanks... (maybe include this in the manuals, I couldn't find this
> information...)
It is:
http://developer.postgresql.org/docs/postgres/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS
---
On Wed, Apr 27, 2005 at 13:56:02 +0100,
deepak <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
This isn't a bug, its a question. I am moving the discussion over to
the general list.
> Bug reference: 1633
> Logged by: deepak
> Email address: [EMAIL PR
On Thu, May 12, 2005 at 10:40:34 -0500,
Celia McInnis <[EMAIL PROTECTED]> wrote:
> Thanks very much Bruce and Tom for your responses and explanations. The
> current mode of operation is mathematically disturbing so I'm hoping that you
> can figure out some sort of a fix! Perhaps this example is
On Mon, May 23, 2005 at 11:04:36 -0400,
"Goar, Saul" <[EMAIL PROTECTED]> wrote:
> Do you have a Bulletin Board, or web site for questions and answers.
There are FAQs referenced off the Postgresql web site.
If you want to ask specific questions than you should use the appropiate
mailing lists. T
On Tue, May 31, 2005 at 11:15:23 -0400,
Alvaro Herrera <[EMAIL PROTECTED]> wrote:
>
> (Note that our ~ regexes are powered by code of Tcl's heritage, so you
> could check Tcl's manual on regexes.)
Aren't they based directly on Henry Spencer's code?
---(end of broadcast)
This does not belong on the pgsql-bugs list. The pgsql-novice or
pgsql-performance lists seem more appropiate. I have set followups
to the pgsql-novice list.
On Thu, Jun 02, 2005 at 12:05:00 +0100,
Bahadur Singh <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I found situtation that, when I am selec
On Thu, Jun 02, 2005 at 20:22:07 +0100,
Mauro Delfino <[EMAIL PROTECTED]> wrote:
>
> I have the these two tables:
> CREATE TABLE table_one
> ( field1 VARCHAR(255) );
>
> CREATE TABLE table_two
> ( field1 VARCHAR(255) UNIQUE );
>
> table_one has 500k records. I certify that all strings are dist
1 - 100 of 121 matches
Mail list logo
