The following bug has been logged online:
Bug reference: 4281
Logged by: thomas
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Windows 2003
Description:some types of errors do not log statements
Details:
this isn't really a bu
The following bug has been logged online:
Bug reference: 5049
Logged by: Thomas
Email address: m...@alternize.com
PostgreSQL version: 8.4.0
Operating system: Debian lenny
Description:query crashing backend with TRAP: FailedAssertion
Details:
while trying out the
The following bug has been logged online:
Bug reference: 2973
Logged by: Thomas
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.2
Operating system: IRIX 6.5
Description:Compile Error with MIPSpro compiler
Details:
During building the project with gmake I
The following bug has been logged online:
Bug reference: 3259
Logged by: Thomas
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: WinXP SP2
Description:Problem with automatic string cast
Details:
I have this SQL:
select * from (select
The following bug has been logged online:
Bug reference: 1502
Logged by: Thomas
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: N/A
Description:hash_seq_search might return removed entry
Details:
The hash_seq_search keeps track of what
thomas wrote:
The following bug has been logged online:
Bug reference: 4281
Logged by: thomas
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Windows 2003
Description:some types of errors do not log statements
Details:
this isn&#
The following bug has been logged online:
Bug reference: 4661
Logged by: Thomas Waelde
Email address: tho...@waelde.de
PostgreSQL version: 8.3.5
Operating system: Linux (Ubuntu 8.10)
Description:Installation
Details:
Configring the installation as
./configure
Hello Greg, Hello Devrim,
i will follow zour hints and answer back to you on it.
I prefer to install SW like this via the source-code.
Nevertheless thanks a lot
Thomas
Craig Ringer schrieb:
Devrim GÜNDÜZ wrote:
On Mon, 2009-02-16 at 12:11 +, Thomas Waelde wrote:
i got the following
on the partitioning column.
Best Regards,
Thomas
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
he PG manual should mention something about this together with
a proposed workaround?
Best Regards,
Thomas
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
r now I will need to get this working on 8.2.x.
Does this leave me with UPDATE triggers as the best viable (is it
viable?) solution?
Are there, as mentioned in previous post, some way to simulate the way
the DB behaved when using rules for partitioning?
Best Regards
Thomas
--
Sent via pgsql-
The following bug has been logged online:
Bug reference: 5139
Logged by: Thomas Kotzian
Email address: thomas.kotz...@repromedia.at
PostgreSQL version: 8.4.1
Operating system: Linux
Description:2pc behaves differently on 8.3 and 8.4
Details:
i upgraded from 8.3
The following bug has been logged online:
Bug reference: 5196
Logged by: Poindessous Thomas
Email address: tho...@poindessous.com
PostgreSQL version: 8.3.8
Operating system: Linux redhat 5.3 x86_64
Description:Excessive memory consumption when using csvlog
Details
/postgres.log start
so we have three logfiles :
postgresql.log (always empty)
postgresql--MM-DD.csv (big file if set to csvlog)
postgresql--MM-DD.log (always empty if set to csvlog)
Thanks.
2009/11/19 Tom Lane :
> "Poindessous Thomas" writes:
>> we have a weird bug. When u
The following bug has been logged online:
Bug reference: 5231
Logged by: Thomas Hamilton
Email address: thomashamilto...@yahoo.com
PostgreSQL version: 8.3.8
Operating system: Ubuntu 4.2.4
Description:SELECT DISTINCT poorly implemented vs SELECT ... GROUP
BY
Details
s the path- and filenames written exactly, with
upper and lower cases. Only pg_ctl.exe ?)
Somme more results:
- In windows, the createt datadirectorys belong to the windows-user
"thomas", with permissions for "administrator" and "postgres",
but not allways (I m
The following bug has been logged online:
Bug reference: 5348
Logged by: Thomas Kellerer
Email address: tho...@kellerer.name
PostgreSQL version: 8.4.2
Operating system: Windows XP
Description:Postgres crashes with index on xpath_string
Details:
With the contrib
Thanks for the feedback.
Is the problem specific to 8.4.2 or to the Windows platform (or both)?
Regards
Thomas
Bruce Momjian, 27.02.2010 18:42:
Yes, we have received a few reports about this and are working on a fix
POSTGRESQL BUG REPORT TEMPLATE
Your
name
:Thomas Swan
Your email address
:[EMAIL PROTECTED
s that
actually the case? Is unixODBC sufficiently mature to consider merging
the efforts?
- Thomas
date->timestamp conversion code gets this right, so you might want
to look at that. From my testing, the only annoying case is for 02:00 on
the day of a DST transition, when you either skip or get an extra hour.
If you still have trouble, I'd be happy to look at your code...
- Thomas
rnal UTC-based
timestamp value based on the current contents of the tm structure.
It *may* be possible to run through some of these steps *twice*, to
verify that the conversion to/from the tm structure including time zone
info gives a result on an even day boundary. But it sounds expensive.
Comments and suggestions are appreciated...
- Thomas
this routine will work without the
time zone fields filled in. Well, no matter what the docs say it seems
to interact badly with my code and I get segfaults a few lines farther
along. I'm poking at it to track down the problem.
- Thomas
shrunk down to one line since it turns out all
required fields were already available :)
Regression tests pass (which I guess tells me that they need some added
cases, since they passed before too); will commit sometime soon.
- Thomas
s case
only affect the interpretation of ambiguous *input*.
You need to specify "Postgres,European" as your date style.
- Thomas
Hello,
My name : Pascale Thomas
My E-mail: [EMAIL PROTECTED]
Configuration : PostgreSQL 6.5.1 on i686-pc-linux-gnu, compiled by gcc
pgcc-2.91.66
I have problems with an array in a table.
The name of the table is "societe", the name of the array is "event_ok
.x server.
- Thomas
> to_char gives incorrect day conversion of the date 2000/03/26.
This is fixed in the current (development) sources.
- Thomas
an create a new database and demonstrate the same problem.
Hope this helps.
- Thomas
broutines.
- Thomas
keep at it ;)
- Thomas
quot;rpm" and got the
following response:
Warning: PostgreSQL query failed: ERROR: parser: parse error at or near
"" in /home/projects/pgsql/ftp/www/html/bugs/bugs.php on line 347
couldn't get bug id
hmmm...
so, I hope someone is reading this email and (much better) maybe ge
package for quite some time). Since the packages have been rearranged (a
necessary evil to get the packaging right), rpm may not understand how
they match up, and you will do better to *uninstall* the previous
packages before installing the new ones.
Regards.
- Thomas
> > If you take any other month than October, it is working fine. So
> > 09-01-2000 + 1 month => 10-01-2000.
> regression=# select ('10-01-2000'::timestamp + ('1 month')::timespan);
> ?column?
> ----
> 2000-10-31 23:00:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yes, you are right, 6.3.2 was installed (which I never knew!) and
contained that postgresql-clients package. After removing the old
packages, everything worked very well.
Thanks a lot for the help!
regards, Thomas
- --
=> PGP key: http://daemon
the coredump as well as the strace output on my webpage:
http://www.0x49.org/~scip/psql-7.0.2-segfault.strace.tar.gz.
Thanks in advance,
Thomas
- --
=> PGP key: http://daemon.de/key.txt
=> "Experience is what you got when
=> you did not get what you wanted."
---
month = 01
> --> 2-digits for day = 11
> --> last '2' is ignored
> With 'YY' *hell* I not sure... add current year IMHO not must be
> correct. I mean that correct solution is:
> test=# select to_date('00-12-11', 'YY-DD-MM');
> ERROR: Can't convert 'YY' to a real year.
> But if users want for their Oracle->PG port use 'YY' as last two digits
> in the current year, not problem make it
Karel, I can help polish the heuristics with you. That 1970/1950
convention is something you can rely on.
- Thomas
s without anyone even asking about edge
cases.
- Thomas
raries when installing
an RPM package for another project.
There were a few unresolved symbols in 4.0 that seem to be available in
another library, but I haven't heard how we finally resolved it.
Is this related to your symptom?
- Thomas
> Short Description
> Updating multiple bool values crashes backend
I cannot reproduce this example with 7.0.2 on my Linux-2.2.16 laptop. We
will need more details and a reproducible example to help out...
- Thomas
at we can read it
in! I'd suggest using pg_dump on the relevant table, but other
techniques can be used.
Regards.
- Thomas
th egcs and gcc-2.95 over and over and over,
without seeing it tickle a compiler bug. You might have some bad memory?
That old 120MHz Pentium must be puffing pretty hard trying to compile
this...
- Thomas
the draft documents we found on the web
last year.
ISO/IEC 9075-2:1999 SQL - Part 2: SQL/Foundation-
September 23, 1999
[Compiled using SQL3_ISO option]
section 7.7 rule 7
- Thomas
problem corrected by building against the above-mentioned .rpmrc
file.
I've cross-posted this to the RPM contact address for Mandrake (hi!) and
would be happy to provide more information.
- Thomas
n or around line 2056. Change a
single line, just under the "case DTK_QUARTER:" from
result = (tm->tm_mon / 4) + 1;
to
result = ((tm->tm_mon - 1) / 3) + 1;
and you should start getting the right answer. Will be fixed in the next
release.
- Thomas
n or around line 2056. Change a
single line, just under the "case DTK_QUARTER:" from
result = (tm->tm_mon / 4) + 1;
to
result = ((tm->tm_mon - 1) / 3) + 1;
and you should start getting the right answer. Will be fixed in the next
release.
- Thomas
sult in signs on all
fields once a negative value is seen, and this seems to be the least
troublesome solution. The patches also put an explicit "day(s)" on the
days field, if any.
Fixes will appear in the next beta (beta4?) unless there are objections.
Let me know if you need the patches.
Thanks for the report!
- Thomas
fields
are signed.
That seems to be less ambiguous. fwiw, the traditional "Postgres format"
never was right in this regard (though internal calculations were done
correctly).
- Thomas
n my 7.0.2 RPM installation, or on my from-cvs
current sources (dow for April 1 comes up as zero, as you would expect).
What machine are you running on, and how did you build?
- Thomas
e zone
behavior, eh?
- Thomas
recently fixed their version of the spec file; hopefully
we will get this folded back into Lamar's spec file before 7.1 goes out.
- Thomas
100.0) / 100.0;
Sure, that's a possibility. There is already a macro to help do that
sort of thing, but I've not jumped to this solution since we probably
should allow some kind of variable precision on date/time types.
- Thomas
*.sgml files.
- Thomas
> now if I delete de database dbname1 and try to create the database dbname2
> it works.
Your hard disk is full??
- Thomas
n (d = null) then '0' else d end from t1;
text
---
1.11784577978351e+253
(1 row)
I haven't tracked it down, but I'll guess that the automatic type
conversion logic is getting confused with the stringy form of zero.
I do not see the symptom in the current development tree.
- Thomas
in "60".
> So if you try to select the value you find "01/01/2001 10:10:60.00 CET".
Get and use the Mandrake RPMs from the ftp.postgresql.org web site. This
is a known problem with the RPMs included in the Mandrake distro, and
their newest builds in cooker should
match strings containing "Sean". Look in the PostgreSQL docs for hints
on how to do case-insensitive searches.
- Thomas
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
an be as simple as (ymmv; I'm doing this from scratch):
create function f(int4) returns f as ...
where the conversion function must be, afaik, compiled code (our SQL
embedded language is too smart to let you pass it through unchanged).
Otherwise, you need to use the second, quoted, style fo
ers around daylight savings time
transitions. Fixed (I believe) in the upcoming 7.1 release.
- Thomas
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMA
x27;/NULL/g" < informix.dump > pg.dump
- Thomas
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
ONE type, which carries no date info for context. And they have no
"date with time zone", which except for a few hours a year might be more
helpful. imho TIMESTAMP is to be preferred in most cases.
- Thomas
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Tom Lane wrote:
>
> Thomas Lockhart <[EMAIL PROTECTED]> writes:
> >> --- ./results/horology.out Mon Apr 2 17:06:59 2001
> >> SELECT time with time zone '01:30' + interval '02:01' AS "03:31:00-08";
> >> 03:31:00-08
&g
now()"? As in
select to_char(date 'today' - 1, '-MM-DD');
which uses the DATE type rather than ABSTIME/TIMESTAMP returned from
now(). That should eliminate the problem, since the DATE type does not
try to carry along time zone information. Seems to wor
in date-to-timestamp conversion (which will
> happen at the input to to_char()).
Ah, right. I had tested in the GMT time zone, which cures all ills :(
- Thomas
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, plea
the Middle East. April 28 is not a significant date in my
time zone, but may be in yours.
- Thomas
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
ed one day back!!!
> Tested on RedHat 7.0, PostgreSQL 7.0.3
We will need more details on your installation to be able to help, since
this is *not* reproducible on most systems. We've never heard of this
before!
- Thomas
---(end of broadcast)--
ou *could*
be doing this as
select date_part('epoch', ) ...
hth
- Thomas
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
The actual implementation does not have to have this, only your
prototype declaration. The function or method name will no longer be
mangled, but of course you can not overload it either.
Good luck!
- Thomas
---(end of broadcast)---
elper function in the driver or backend to
implement it.
Terry, can you research the expected behavior of locate() to confirm
that your test suite is accurate wrt the expected result?
- Thomas
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
o accomodate it.
- Thomas
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
unately all my
> dates are in the format 'dd.mm.ccyy'.
> Is this a bug or a user error?
I'm willing to bet that the date style is *not* set to "European".
Please demonstrate with a "show datestyle" and "select date
'2.10.1997'&qu
xamples please!!
- Thomas
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
te the
bugtool database with the problem resolution? If so, perhaps you could
do that when you have a chance.
- Thomas
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
every possibility, and
you want to reject those with some properties but not others?
If so, you might try using to_date() to enforce a specific input format.
You might find it easier to ingest these into a text column first, then
manipulate from there (for example, you could prepend the century
digits). Bu
stgreSQL
a chance to hold an intermediate result to sort in a second pass.
- Thomas
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
> ... (though the regression tests perhaps
> deserve a share of the blame too, for not covering that case).
> Patch to appear shortly...
Will the patch include a case for the regression test? Or could someone
(other than me??!!) volunteer to cover that?
lue to the left for it to apply to.
In 7.1, a unitless number is not allowed for an interval, at least
partly because SQL9x requires time zones to be considered intervals
under some conditions. So the default handling of intervals had to be
consistant with that usage.
I wo
m go away if you set your time
zone to GMT. Upgrade to 7.1.x.
- Thomas
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
27;07-17-2001'
What is the schema? I'll guess that fecha_emision is not actually a date
type (either date or timestamp) but rather a text field. That is the
only way I can think of to provoke an "external representation" error.
More details please.
- Thom
the schema of the factversionelement table. I will bet that
the "content" column is not in fact a timestamp type (it is some sort of
string type??), and does not contain strings which are entirely legal as
timestamps.
- Thomas
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
that there are variations in content between different vendors (Sun does
a painstakingly accurate job afaict).
- Thomas
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
er of a "fix list" for this beta
cycle? This issue should be on it...
- Thomas
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
...
> I think we have agreed that 'current' is a Bad Idea and should be
> eliminated from the date/time datatypes...
I've started purging it from the timestamp code I'm working on for 7.2.
Should be gone by the start of beta...
- Thomas
e operator seems like a good idea, until proven
otherwise. Will try to get it on my list for the current work.
- Thomas
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
...
> I think that if it actually reused them instead of deleting old files...
That is in fact what it does for at least the upcoming 7.2 release.
- Thomas
---(end of broadcast)---
TIP 5: Have you checked our extensive
> \h select in psql says (among other things)
> [ { UNION | INTERSECT | EXCEPT [ ALL ] } select ]
> I think it should read
> [ { UNION | INTERSECT | EXCEPT } [ ALL ] select ]
I agree. Bruce ("Mr. Backslash" :) are you planning on picking this up?
roblem.
Tom
>>> Tom Lane <[EMAIL PROTECTED]> 10/31/01 21:43 PM >>>
"Thomas Yackel" <[EMAIL PROTECTED]> writes:
> I got the error: "Bad abstime external representation ''" when attempted to start
>psql as a particular user and the po
Gentleman:
Regarding the above thread located at:
http://fts.postgresql.org/db/mw/msg.html?mid=1030673
I got the error: "Bad abstime external representation ''" when attempted to start psql
as a particular user and the postmaster shutdown.
The problem, we discovered, is that this user had a c
hould work; you can set it as
CFLAGS+=... in Makefile.local, or continue to try to get an environment
variable to do what you want (I do not use that technique myself, so
can't help with the nuances, but maybe export CFLAGS="..." with some
quotes will do it).
- Thom
ons without much discussion of the
performance hit.
- Thomas
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
l
real world example afaict.
Do you have another example to illustrate the problem for a query which
one might actually need to use?
- Thomas
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
iew has a column which is
named "user" and which is not directly accessible without using double
quotes.
I'm not sure that would qualify as a bug, but certainly is a gotcha...
- Thomas
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
in 'tude on the nannyism issues; I like building bigger guns too
;)
- Thomas
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
0:00:00'?
> not that i ever expect to encounter that macaddress in the field, but
> for consistency's sake...
> i just tested 'ff:ff:ff:ff:ff:ff', and it works fine.
Already fixed in the upcoming 7.2. Thanks for the report.
- Thomas
--
e you can set time zones or, if you have a fixed query
with date in and date out, and intervals which are multiples of a day,
then you can simply add 12 hours in the query to get the rounding you
expect:
cast((date '2001-10-28' + interval '1 day' + interval '12 hours'
ons for SET
DATESTYLE in that doc; in particular, the claim that DATESTYLE is really
intended only to help with porting applications is a bit misleading
imho. I'll check the wording for the upcoming release...
- Thomas
---(
Running postgresql 7.1.3:
I have a timestamp column in my table and I want to select all rows either
elder or newer than 14 days.
SELECT * FROM table WHERE column > CURRENT_TIMESTAMP-'14 days'::interval
SELECT * FROM table WHERE column < CURRENT_TIMESTAMP-'14 days'::interval
Postgresql refuses to
lockhart=# select date '02.09.01';
2001-02-09
lockhart=# select date '02.09.00';
2000-02-09
lockhart=# select version();
-----
PostgreSQL 7.1.2 on i686-pc-linux-gnu, compiled by GCC 2.96
thomas=# select date '02.09.00';
date
2000-02-09
> Just discovered that column::date works fine but to_date(column, 'DD.MM.YY')
> causes the problem. I was trying to write portable SQL, but never mind!
Portable (as in SQL9x) would be
cast(column as date)
which is also accepted by PostgreSQL...
vior required by SQL9x afaicr.
There is another function (timeofday()?) which returns the current clock
time.
hth
- Thomas
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
1 - 100 of 264 matches
Mail list logo
