The following bug has been logged online:
Bug reference: 3632
Logged by: andrew
Email address: [EMAIL PROTECTED]
PostgreSQL version: postgresql-8.2.
Operating system: winxp
Description:couldn't start postgreSQL
Details:
Hello
when i use postgresql-8.2.m
The following bug has been logged online:
Bug reference: 1920
Logged by: Andrew
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1-B2 (win32)
Operating system: XP Professional
Description:Installer no WIN1252 & UTF8 selection
Details:
I can't selec
The following bug has been logged on the website:
Bug reference: 7622
Logged by: Andrew Gierth
Email address: and...@tao11.riddles.org.uk
PostgreSQL version: 9.2.1
Operating system: n/a
Description:
Tested on git-master, 9.2.1, various older versions.
select (select
The following bug has been logged on the website:
Bug reference: 7881
Logged by: Andrew Gierth
Email address: and...@tao11.riddles.org.uk
PostgreSQL version: 9.2.3
Operating system: any
Description:
The range type code accepts SQL functions for subtype_diff, but
The following bug has been logged on the website:
Bug reference: 8274
Logged by: Andrew Gierth
Email address: and...@tao11.riddles.org.uk
PostgreSQL version: 9.1.9
Operating system: any
Description:
The guy on IRC who ran into this one was using 9.1.9, but it seems
The following bug has been logged on the website:
Bug reference: 8453
Logged by: Andrew Gierth
Email address: and...@tao11.riddles.org.uk
PostgreSQL version: 9.3.0
Operating system: any
Description:
The first snprintf in writeTimeLineHistoryFile in receivelog.c
The following bug has been logged online:
Bug reference: 4328
Logged by: andrew victoria
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: fedora core 9
Description:help in creating database encoded with LATIN1
Details:
i got an error
10 is the same every time, but rdi changes.
Andrew
ECC memory, RAID 10 w/ adaptec 3405 hardware controller. Period between
crashes ranged from about 1min-5mins. Just switched to a new box so the
problem is "gone". In the original email I meant ubuntu 6.06.
On Wed, Jul 30, 2008 at 12:06 AM, John R Pierce <[EMAIL PROTECTED]> wrote
a terrible idea. (Frankly, they're a
terrible idea outside that context also, but that ship sailed some
time ago.)
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.commandprompt.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
do that for 8.4, and just backpatch the
O_BINARY flag to these two locations for 8.3 and 8.2. Thoughts?
ISTR there are a few places where we want CRLF translation (config files?)
I'd be fairly conservative about making changes like this.
cheers
andrew
--
Sent via pgsql-bugs mailing
s far as he could see.
cheers
andrew
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
that you should invent
OpenConfigFile() or some such. But it hardly seems worth it.
cheers
andrew
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ng the question. I
think you have your answer, even if you don't like it.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
+1 503 667 4564 x104
http://www.commandprompt.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mai
The following bug has been logged online:
Bug reference: 4486
Logged by: Andrew Grillet
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3
Operating system: Windows XP
Description:CSV feature request
Details:
Excel 2007 decides on the fly whether to quote
way of allowing the more traditional way of calling sort routines, send
it in. Sharing globals between the Safe and non-Safe worlds is not a
solution - we removed an instance of that not long ago for security reasons.
cheers
andrew
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Alex Hunsaker wrote:
On Tue, Nov 4, 2008 at 15:02, Alex Hunsaker <[EMAIL PROTECTED]> wrote:
On Tue, Nov 4, 2008 at 14:43, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
But by all means if you can come up with a robust way of allowing
the more traditional way of calling s
se variables in the main package. That is, sort is
nathan> setting $main::a and $main::b, and when you run the plperl
nathan> code in the safe compartment, main:: isn't visible any more.
Nice theory, but completely wrong: sort creates $a and $b in the
current package, not in mai
en you build perl with
threading turned off.
--
Andrew.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
lure. It seems to occur ONLY if perl was
built with threading support (ithreads). Without ithreads, I can't
reproduce it (I've tried enabling and disabling multiplicity with no
effect, so it's not that).
Ithreads seem to be the default on many linux package builds of perl.
It is _not_ the
age
3) any operation that relies on CopSTASH(PL_curcop) (I can only find a
few: sort, reset, and bless) will then behave incorrectly
However, I have no idea why Perl has this difference between threaded
and non-threaded code.
--
Andrew.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
>>>>> "Alex" == Alex Hunsaker <[EMAIL PROTECTED]> writes:
Alex> I submitted http://rt.perl.org/rt3/Public/Bug/Display.html?id=60374
Feel free to add my explanation to that (I couldn't see an obvious way
to do it myself)
--
Andrew.
--
Sent
ed as working for every SQL query
executed in the function, rather than for a specific list of
constructs, this is clearly a bug.
--
Andrew (irc:RhodiumToad)
--
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, Nov 23, 2008 at 05:36:13PM +0100, toruvinn wrote:
> Actually, I prefer it the old way. I just like to know the column order
> `SELECT *' would return (though I never use `SELECT *' myself). Not to
You can't know that, as a matter of SQL semantics.
A
--
A
On Mon, Nov 24, 2008 at 01:39:48AM -0500, Andrew Sullivan wrote:
>
> You can't know that, as a matter of SQL semantics.
I shouldn't reply to listmail when bone tired. I was thinking of
rows. Sorry.
A
--
Andrew Sullivan
[EMAIL PROTECTED]
--
Sent via pgsql-bugs mailing
The following bug has been logged online:
Bug reference: 4553
Logged by: Andrew Gierth
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3-8.4
Operating system: all
Description:HOLD cursors not materializing results fully
Details:
(tested on 8.3.5 and HEAD as
it is what I
think it is, the problem is with libc not postgres.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged online:
Bug reference: 4667
Logged by: Andrew Shved
Email address: ash...@symcor.com
PostgreSQL version: 8.3.5
Operating system: Sun Sloaris 10 SPARC 64 bit ( SunOS 5.10)
Description:pg_standby error on Solaris 10 SPARC 64 bin
The following bug has been logged online:
Bug reference: 4717
Logged by: Andrew Smith
Email address: laconi...@gmail.com
PostgreSQL version: 8.3.7
Operating system: Windows XP
Description:Installing PostGIS via StackBuilder gives an 'Error
opening file' err
ess likely to produce shot feet, IMNSHO. I get very nervous
every time I have to touch it.
cheers
andrew
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Simon Riggs wrote:
On Fri, 2009-05-15 at 10:17 -0400, Andrew Dunstan wrote:
This whole area is unfortunately way too fragile. We need some way of
managing these facilities that hides a lot of these details and is
therefore less likely to produce shot feet, IMNSHO. I get very nervous
The following bug has been logged online:
Bug reference: 4821
Logged by: Andrew Gierth
Email address: and...@tao11.riddles.org.uk
PostgreSQL version: 8.3-8.4
Operating system: all
Description:LIKE '%_' fails
Details:
# select 'foo'
) line 807
FreeSid(psidUser) should be HeapFree(GetProcessHeap(), 0, psidUser)
in order to work with my suggested changes in GetUserSid().
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
address you tried to free.
Although the FreeSid call causes no harm because its defensive, there is
still the issue of leaking the TOKEN_USER structure.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes
ToDacl() is the only
function making use of GetUserSid(), so this change won't break
anything. The benefit to this approach over my first suggestion is that
it avoids an unneeded HeapAlloc(sid), CopySid(sid) ... and its cleaner.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://ww
wasn't sure if someone wanted that way. I'd suggest
malloc and free if your going to change it. The only time I use an MS
allocater is when a win32 api function specifically states it must be used.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via
n the same message becomes far more unlikely.
Also, they end up being more efficient than sha256 by itself.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
Attached is a mix of our two patches. How does that look to you?
looks good.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
o 8.5.
Hard to keep that win32 acl stuff leak free. There is always a cleanup
goto because you need 6 billion objects to answer any question :o
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make
| 77.202.22.228
| 3 | 37349 || 2009-05-09 13:40:09.031336
(79870,5) | 16395 |0 |0 |0 | 15722953 | 0 | 77.202.22.228
|56 | 0 || 2009-05-09 13:40:23.072695
(above 3 rows are)
(full list at http://pastebin.com/m16600dc8
nd event?
The system was recently dump/restored from a different box. The
failing rows are all new inserts since the restore.
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
like a probable explanation, but that idea
Tom> goes out the window if there have been no UPDATEs.
No UPDATEs (and there are no HOT flags set on any tuple I looked at).
There may have been DELETEs.
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.o
6f 00 00 |.o..|
0ae0 00 15 5a 02 00 0a 00 00 00 02 00 00 00 00 00 00 |..Z.|
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ffected table).
However I'm wondering if another 8.3.4 fix, the RecentGlobalXmin one,
could be relevant here?
http://archives.postgresql.org/pgsql-committers/2008-09/msg00105.php
(I'm not seeing how it would be, but... note that the xids have got
to the point that they'd appear to
anything with it, it was almost certainly already broken (or
possibly 6179 broke it).
Notice that in the log table, the log entry that records the most
recent update to the row is the one with xmin=4971. There is no
entry in the log table corresponding to 6179.
--
Andrew (irc:RhodiumToad)
--
Sent via
The following bug has been logged online:
Bug reference: 5048
Logged by: Andrew Deryabin
Email address: and...@deryabin.com
PostgreSQL version: 8.4
Operating system: FreeBSD
Description:psql: \g doesn't redirect COPY TO STDOUT, but redirects
next query
Details:
The following bug has been logged online:
Bug reference: 5053
Logged by: Andrew Gierth
Email address: and...@tao11.riddles.org.uk
PostgreSQL version: 8.5devel
Operating system: FreeBSD
Description:domain constraints still leak
Details:
Domain NOT NULL constraints
age
pd_lower while leaving the rest of the page intact.)
I did ask Bryan on IRC to make a copy of his data directory before doing
the fix.
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
qual is being dropped somewhere, which changes
the output since that's a disguised not-null condition.
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
om> doesn't seem like that's going to come up enough to be worth
Tom> stressing about. If we wanted to be smart about it we'd have to
Tom> have two kinds of single-element equivalence classes (one that
Tom> implies a k = k check is needed, and one that does
oesn't matter. Leaving the clause out of the
Tom> equivalence machinery is certainly safe; at worst we'll end up
Tom> with a redundant test or two in the final plan.
Yeah, and clearly leaving in that kind of redundant test is no big
deal.
--
Andrew (irc:RhodiumToad)
The following bug has been logged online:
Bug reference: 5087
Logged by: Andrew Gierth
Email address: and...@tao11.riddles.org.uk
PostgreSQL version: any
Operating system: any
Description:Submitted bug reports not showing up in a timely manner
(or at all)
Details
an impression
based on the number of cases in which I am later reminded of the bug and
go back to look for it.)
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
and don't see that I ever got a
Joshua> notice that I needed to approve #5085. I did get one for 5804
Joshua> and 5806, FWIW.
That's what I was afraid of; it rather suggests that some submissions are going
astray without any moderator ever seeing them. Someone should probably check
ds; specifically it doesn't contain enough row
visibility info for index-only scans to be possible without consulting
the table.
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
any
new cases; we'll have to take your word for that :-)
The code around this has changed a little on -head. I don't have any
more spare cycles at the moment - are you able to produce an updated
patch for 8.5?
Andrew/Magnus; we do still see occasional failures of this nature, so
I believ
s to pick it up :-)
I'd rather wait till you can check it.
cheers
andrew
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
rt_to is defined as stable rather than immutable. (Sure it depends
on server_encoding, but that can't exactly change... if there's any
other reason why it's not immutable, I can't think what it is.)
Example (5) from the original message is the correct approach in any
case;
like a bit of a stretch to me... we treat lots of stuff as
immutable which is actually easier to change than pg_conversion entries
(OS locale definitions for example).
--
Andrew.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
y are coded
for).
Of course, changing the definition of a locale will break everything
until you reindex, etc., but we put up with that because the
alternatives are clearly silly.
--
Andrew.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
te or replace function foo2(r foo2) returns foo2 language plpgsql
as $f$ declare v foo2; begin v := r; return v; end; $f$;
select foo1(null);
foo1
--
(,)
(1 row)
select foo2(null);
ERROR: cannot assign non-composite value to a row variable
CONTEXT: PL/pgSQL function "foo2" whil
The following bug has been logged online:
Bug reference: 5200
Logged by: Andrew Masterton
Email address: a.j.master...@open.ac.uk
PostgreSQL version: 8.3.8
Operating system: RedHat Enterprise 5.4
Description:Use of min suffix in autovacuum_naptime ignored
Details
everything else inherits that. All
setrlimit calls for RLIMIT_STACK are explicitly clamped to MAXSSIZ, so
there's no way to set that value higher than the kernel limit, and no
way for getrlimit to report a value higher than the real limit.
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-bugs
Oleg> The most interesting thing is that this function makes segmentation
Oleg> fault also on FreeBSD 7.2 with Postgresql-8.3.7.
What are the definitions of your instr() and ad_parent_tree() functions?
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgres
>>>>> "Andrew" == Andrew Gierth writes:
Andrew> What are the definitions of your instr() and ad_parent_tree()
Andrew> functions?
Well, there's so much wrong with that ad_parent_tree function - it's
always going to recurse infinitely (with a new subxact
do something like this: before deparsing,
walk the query looking for offending USING clauses, and make a list of
renamings to apply to column names.
I haven't tried actually implementing this, but I believe it is
possible.
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
he function as volatile fixes the
David> issue. Possibly related to BUG #4907.
I don't think it's particularly closely related to #4907.
I've confirmed this bug still exists in both 8.4.2 and HEAD; it's
clearly a problem that affects only inlined SQL functions (making the
>>>>> "Tom" == Tom Lane writes:
> Andrew Gierth writes:
>> I don't think it's particularly closely related to #4907.
Tom> Yeah.
BTW, did #4907 ever get fixed in the back branches?
--
Andrew (irc:RhodiumToad)
--
Sent via pgsql-bugs m
The following bug has been logged online:
Bug reference: 5296
Logged by: andrew neill
Email address: andrew.nei...@bbc.co.uk
PostgreSQL version: 1.10
Operating system: windows xp
Description:crash when two 'add column' diagrams are open
Details:
if yo
null
line_text varchar(254)
The output is as follows:
perl t2 x
2: ERROR: Unterminated quoted string
-
Andrew BrownE-Mail: mailto:[EMAIL PROTECTED]
Senior Systems Engineer Phone: +61 7 4928 1020
ADC/Saville Systems Fax:+61 7 4928 1082
Web
backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!#
I am running PostgreSQL 7.0.2 on FreeBSD 3.4-STABLE (x86). Thanks,
- Andrew.
11:14 \_
/usr/lib/postgresql/bin/postgres localhost andrew newsfeed
UPDATE
That's right now, so it's frozen on an 'UPDATE' and looking at my (perl)
program the only 'UPDATE' is this one:
UPDATE stor
{"not","other","full"}
{"not","other","empty"}
(2 rows)
testing=# update t1 set c1[3] = 'full';
UPDATE 2
testing=# select * from t1;
c1
2
tarball for linuxppc.
I have also built postgresql 7.0.2 for i686 (RedHat 6.1) but the problem
is not evident on that architecture.
Cheers,
Andrew
solution.
something like:
set CENTURY_WINDOW TO '1980';
Would be nicest.
Regards,
Andrew.
--
_____
Andrew McMillan, e-mail: [EMAIL PROTECTED]
Catalyst IT Ltd, PO Box 10-225
I just installed v7.0.3 release on a FreeBSD 4.x system. (Problem still happened in
7.0.2 too).
This is the problem I noticed:
# select * from mailredirs;
username |destination | start | stop |
reason
--++
contains a value of "Just because."
# select * from values where value LIKE 'Just because.';
id | attributeid | thingid | value
---+-+-+---
13525 | 46 |1246 | Just because.
(1 row)
Regards,
Andrew.
On Wed, 15 Nov 2
i love postgresql | 2000-11-10 17:25:45+11 | 2000-11-20 17:25:45+11 | Tom Lane r0x0rs
(1 row)
foo=# SELECT * FROM Depressed WHERE Start < CURRENT_TIMESTAMP AND Stop >
CURRENT_TIMESTAMP;
ERROR: Bad timestamp external representation 'i love postgresql'
Bingo!
Hope that helps,
Andrew.
0
> , not 7.0
>
> No file was uploaded with this report
>From the line break in the "should be 7.0
, not 7.0" I wonder if it isn't a CRLF vs LF problem?
Regards,
Andrew.
--
__
t; Materialize (cost=50101.13..50101.13 rows=6577 width=12)
> -> Seq Scan on marche (cost=0.00..50101.13 rows=6577 width=12)
> EXPLAIN
>
> - but it takes to many time: (after about 16 hours I interrupt the query)
This is a known bug
Simple add lines as shown:
> for r in select * from tconcattest loop
IF r.str IS NOT NULL THEN
> output := output || r.str;
END IF;
> end loop;
- Andrew
A few hours ago, I wrote:
>
> Simple add lines as shown:
>
> > for r in select * from tconcattest loop
> IF r.str IS NOT NULL THEN
> > output := output || r.str;
> END IF;
> > end loop;
>
This would probably be bet
for a change.
Make one of your arguments a text string containing multiple of your real
arguments. Inside your function split it up into it's original constituents.
You should be on 7.x though. Really.
Cheers,
Please see FAQ 4.9
http://postgresql.bteg.net/docs/faq-english.html#4.9
On Fri, 15 Jun 2001, Alexandr S. wrote:
>
> Bug: the index on INTEGER field does not work (PG 7.1.2).
>
> Test 1:
>
> 1) create table test_int(id int primary key);
>
> 2) insert 1 records in table test_int with perl
Hi
I'm have problems checking the descripton of
the table when using \d with the tablename.
I've correctly created the database and can
insert/query the tables so they are definetly there.
The error message I get for
\d kids;
is
Did not find any relation named "kids;".
The v
POSTGRESQL BUG REPORT TEMPLATE
Your name : Andrew Pimlott
Your email address : [EMAIL
Hello.
I'm using debian on i386 with postgresql 7.1.3.
I'm writing an interface libary to postgresql which uses libpq, and
I've stumbled across a weird problem and i'm having problems tracking
down.
Oh and sorry about bad code formating, evolution an't giving me as much
room as i want.
main()
as why it
seemed like a strange change to me.
Sorry to have not read the migration issues before filing this - I
thought from following these mailing lists that I knew them already :-)
Cheers,
Andrew.
--
Perhaps I'm missing something here, but it looks like I'm getting an
insert into both the parent and child tables when my RULE's where
clause is based on a DEFAULT generated from a sequence. It looks like
nextval on the sequence is called 3 times for every insert.
I don't know if this is properly
t causes the AM/PM indicator simply to never work except at the end of
the string, I see no possible justification for not backpatching the fix.
--
Andrew, Supernews
http://www.supernews.com - individual and corporate NNTP services
---(end of broadcast)-
ut I'm not going to risk back-patching
> it without some field testing.
>
Hmm. That negative pointer hack is mighty ugly.
I am also wondering, now that it's been raised, if we need to issue a "use
utf8;" in the startup code, so that literals in the code get the right
enco
"workaround" was to stop the source DB server and redo the
backup.
My (somewhat speculative) conclusion is that there may be a problem with
performing hot-backups on a live database.
Andrew.
BACKUP:
pg_dump.exe -i -h localhost -p 5432 -U Administrator -F c -b -v -f
"D:\dbname
eginning to think that domains
> constrained not null are just fundamentally a bad idea.
>
I think we just expect left joins to produce nulls regardless of
constraints on the underlying cols, don't we? Concluding that not null in
domains is bad seems a bit drastic.
cheers
andrew
-
The following bug has been logged online:
Bug reference: 3089
Logged by: Andrew White
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: SuSE Linux 9
Description:View/Table Creation/Ownership Bug
Details:
To Whom It May Concern,
I came
The following bug has been logged online:
Bug reference: 3092
Logged by: Andrew Rass
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: FreeBSD 6.2
Description:character varying and integer cannot be matched
Details:
Hello the following
int32, and the
documentation says nothing about a limit - I'm sure it's just a 32-bit
counter in the kernel). I'll give that a shot.
Linux manpage suggests local max is 32767, so that's probably a good
value to try.
cheers
andrew
-
The following works as expected:
select (SELECT CASE WHEN (1=2) THEN 0 ELSE sum(count) END) from (
select 1 as count union select 2 union select 3
) as "temp";
The result is "6".
The following also works as expected:
select count(*) from (
select 1 as count union select 2 union select 3
) as "
ther this is a bug for postgres seems to depend on whether that
reading is coming from the OS or postgres itself. (I don't know the
answer to that.)
A
--
Andrew Sullivan | [EMAIL PROTECTED]
In the future this spectacle of the middle classes shocking the avant-
garde will p
to be pretty clear that the scope
info is a necessary part of the addressing, so I don't think it can
be thrown away before looking at the address.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
I remember when computers were frustrating because they *did* exactly what
you told them to.
a configuration to the Internet. All my
experience tells me that such things eventually always leak, and I'd
hate for Postgres to be the source of that sort of damage.
A
--
Andrew Sullivan | [EMAIL PROTECTED]
The whole tendency of modern prose is away from concrete
1 - 100 of 260 matches
Mail list logo
