The following bug has been logged online:
Bug reference: 3799
Logged by: depesz
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3 HEAD
Operating system: linux, 32bit
Description:csvlog skips some logs
Details:
when settings are set to:
# select name, setting
now.
But. Since you're using Ubuntu, you can install postgresql-client-8.2
package, and use psql from it.
Best regards,
depesz
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ls-vs-not-in/
Best regards,
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: [EMAIL PROTECTED] / aim:depeszhdl / skype:depesz_hdl / gg:6749007
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscr
matches('/a/b[534]', E'(.*)\\[([0-9]*)\\]');
regexp_matches
{/a/b,534}
(1 row)
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: [EMAIL PROTECTED] / aim:depeszhdl / skype:depesz_hdl / gg:6749007
--
S
l.org:/pub> cd source/v8.2.10
cd ok, cwd=/pub/source/v8.2.10
Best regards,
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: [EMAIL PROTECTED] / aim:depeszhdl / skype:depesz_hdl / gg:6749007
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgre
rator does not exist: hstore -> boolean
LINE 1: select tconvert('a', 'b')->'a' is null;
^
HINT: No operator matches the given name and argument type(s). You might need
to add explicit type casts.
([EMAIL PROTECTED]:5840) 15:14:03
ange the regexpin substring to:
'^[0-9]{10}(?:,[0-9]{10})*$'
2. change check to:
CHECK ((public_phone ~ '^([0-9]{10}(,[0-9]{10})*)?$')));
choose whichever you prefer.
Best regards,
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gt
On Thu, Feb 05, 2009 at 12:11:51PM +, Eduard Deacoon wrote:
> WHERE '' || QUOTE_IDENT($3) || '' = '' ||
> $4||''::TEXT'' ||
make it:
WHERE '' || QUOTE_IDENT($3) || '' = '' ||
quote_literal($4)||'&#
On Tue, Feb 10, 2009 at 01:04:02AM +0100, Daniel Migowski wrote:
> SELECT y(); -- fails with:
when you return set, you should use:
select * from y();
select function() is additional feature of sql functions.
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.
t;,
"CAUTION", "IMPORTANT", "NOTE", "TIP", "WARNING", "BLOCKQUOTE",
"INFORMALEXAMPLE" start-tag
openjade:libpq.sgml:310:19:E: end tag for "PARA" omitted, but OMITTAG NO was
specified
openjade:libpq.sgml:254:10: star
ive/libpq-pgpass.html
Best regards,
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: dep...@depesz.com / aim:depeszhdl / skype:depesz_hdl / gg:6749007
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to yo
elect distinct on (x) x, y from test;
x | y
---+---
1 | 2
2 | 3
(2 rows)
# select * from test;
x | y
---+---
1 | 2
2 | 3
1 | 4
(3 rows)
Best regards,
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: dep...@depesz.com / aim:depeszhdl / skype:depes
On Wed, May 20, 2009 at 09:37:56AM +, jose soares wrote:
> I'm trying a NOT IN clause, but seems it doesn't work. Please take a look:
the problem you're experiencing is described in here:
http://www.depesz.com/index.php/2008/08/13/nulls-vs-not-in/
Best regards,
depesz
On Wed, Jun 10, 2009 at 12:38:14PM +0200, Andreas Mutota wrote:
> I could create database and tables but I cannot populate data into any of
> the tables.
what do you mean by "cannot populate"? what commands are you using? what
are the error messages?
Best regards,
depesz
--
ure if it this (rather obscure) functionality is really worth the
trouble.
Best regards,
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: dep...@depesz.com / aim:depeszhdl / skype:depesz_hdl / gg:6749007
--
Sent via pgsql-bugs mailing list (pgsq
On Thu, Jun 18, 2009 at 10:03:21AM -0400, Tom Lane wrote:
> hubert depesz lubaczewski writes:
> > # create table sold_products (items int4, product_id int4);
> > # create table products (id int4, codename text);
> > # select sp.count, p.codename from sold_products
y it works:
# INSERT INTO test (i) values (1), (2), (3);
INSERT 0 3
# update test set i = i + 1;
UPDATE 3
shouldn't it raise exception? and work *only* if i set the constraint to
deferred?
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk:
Hi,
tried on latest 8.5, and some 8.3:
# select '4817191.623 ms'::interval;
interval
--
-00:35:47.483648
(1 row)
I am pretty sure the answer is wrong. But why?
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/
ossibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat
your command.
STATEMENT: vacuum
if yes - how many vacuum jobs there were?
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: dep...@d
well, the question is in subject.
basically - shouldn't this command raise error instead of creating index
named "concurrently"?
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: dep...@depesz.com / aim:depeszhdl / skype:depesz_h
t type(s). You might need
to add explicit type casts.
direct usage of array of course works:
# select 1 = any ( '{1,2}'::int4[] );
?column?
--
t
(1 row)
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: dep...@depesz.com / ai
t('epoch'::text, timezone('UTC'::text,
to_ts)=((1232078399,1232078399),(1231387200,1231387200)).
Please not that both box values are the same, and relate to row:
( '2009-01-08 00:00:00 EST', '2009-01-15 23:59:59 EST' )
while I would assume that one
lyze every 5000 inserts) does modify this behaviour to much
more reasonable.
is this something we are missing or another bug in postgresql?
the selects and inserts are made through plpgsql function (single call
select function(args) does select and insert), but i doubt if this
matters.
depesz
nt record is at 0/5A5508
LOG: redo record is at 0/5A5508; undo record is at 0/0; shutdown TRUE
LOG: next transaction id: 180; next oid: 16844
LOG: database system is ready
FATAL: Bad abstime external representation '"depesz'
FATAL: Password authentication failed for user "pgd
be neccessary - i understand that we
need to wait for transactions in the same db, but waiting for
transaction in another database?
i tested it on 8.2.4 and 8.3devel from cvs-head, fetched 3 days ago.
depesz
--
quicksil1er: "postgres is excellent, but like any DB it requires a
highly pai
user depesz is superuser. i connect to depesz database, and:
([EMAIL PROTECTED]:5830) 14:20:34 [depesz]
# revoke usage on schema pg_catalog from public;
REVOKE
now, i reconnect to the same database with test user (which is not
superuser):
([EMAIL PROTECTED]:5830) 14:23:55 [depesz]
> \d
ER
On Mon, Sep 10, 2007 at 10:38:34AM -0400, Tom Lane wrote:
> hubert depesz lubaczewski <[EMAIL PROTECTED]> writes:
> > # revoke usage on schema pg_catalog from public;
> > REVOKE
> This is not a supported operation.
ok, but i belive it should either dont allow admin to do
n no position to ask to give the ability to revoke the
privileges. all i'm asking is to put some consistency - either break it,
or forbid. but dont say "revoked" when it's not really true.
depesz
--
quicksil1er: "postgres is excellent, but like any DB it requires a
highly p
autovacuum process, a couple of minutes later it restarted! still
nothing in logs.
any ideas?
unfortunatelly i can't do much as this is production server, but perhaps it
will "ring the bell" and somebody will know what to fix.
depesz
--
quicksil1er: "postgres is excellent
sorry to bother you. problem has been found, it's the (default, too low)
value of autovacuum_freeze_max_age.
depesz
--
quicksil1er: "postgres is excellent, but like any DB it requires a
highly paid DBA. here's my CV!" :)
http://www.depesz.com/ - blog d
| Owner
+--+--+
public | x| sequence | depesz
(1 row)
# alter sequence x owner to pgdba;
ERROR: syntax error at or near "owner"
LINE 1: alter sequence x owner to pgdba;
^
# alter table x owner to pgdba;
ALTER TABLE
# \d
List of relations
Sc
On Sun, Dec 09, 2007 at 03:32:17PM +, Simon Riggs wrote:
> ALTER SEQUENCE blah INCREMENT BY val;
this has the sideeffect that all concurrent nextvals() will also
increment by val, which is not always acceptable.
depesz
--
quicksil1er: "postgres is excellent, but like any DB it re
not obvious for everybody, so maybe the message should be cleared
a bit in this case.
on the other hand - i'm not really sure that update rights should be neccessary
in such case.
best regards,
depesz
--
quicksil1er: "postgres is excellent, but like any DB
p/2007/09/06/postgresql-gotchas/
anyway - it's definitely not a bug.
depesz
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
update-account-set-password-new_password-oops/
Best regards,
depesz
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
t_id
2. have a lot of rows in this table
3. very little rows have given merchant_id
you can easily fix the situation with:
create index q on clients (merchant_id, id);
depesz
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
9.6c-3
automake-1.6.3-1
autoconf-2.53a-1
cpp-2.95.4-0.20010823.3
libtool-1.4.2-11
do you have any idea on what is wrong?
depesz
--
hubert depesz lubaczewski http://www.depesz.pl/
-
xx to test;
select relacl from pg_class where relname='czasy';
drop user test;
select relacl from pg_class where relname='czasy';
right now it's not even possible to revoke this rights:
# revoke all on xxx from test;
ERROR: user "test" does not exist
[[loca
x27;m not sure if i'm clear about it.
depesz
--
hubert depesz lubaczewski http://www.depesz.pl/
> wynajmę mieszkanie - 60 metrów, 3 pokoje, piastów - od lutego (po <
-=> remoncie) interesuje cię - napisz: [EMAIL PROTECTED]<=-
msg05634/pgp0.pgp
Description: PGP signature
error message
is totally misleading. can this be improved somehow?
i'm using 7.4devel from cvs.
depesz
--
hubert depesz lubaczewski http://www.depesz.pl/
> wynajmę mieszkanie - 60 metrów, 3 pokoje, piastów - od lutego (po <
-=> remoncie) interesuje
unlimited row size for system tables... ok
initializing pg_depend... /home/pgdba/work/bin/initdb: line 716: 26438 Segmentation
fault "$PGPATH"/postgres $PGSQL_OPT template1 >/dev/null <
do you have any idea on what is wrong?
depesz
--
hubert depesz lubaczewski
rated by literally '\t', and not by tab-space
character.
yet, entering the same in psql as \f '\t' works great.
i belive this is just simple ommision in argument parsing, but i belive
it should be corrected to maintain uniform way of communication with
user.
best regards
h
e that allowing \t in psql and
not allowing \t from commandline is bug and should be fixed.
depesz
--
hubert depesz lubaczewski http://www.depesz.pl/
i choose to hate people when they're not polite; bruise me; that's allright.
can even do:
psql -c "something" -F "something_weird" | sed 's/something_weird/
/g'
yet - this is inconsistency - between different methods of setting
particular parameter.
depesz
--
hubert depesz lubaczewski http://www.depesz.pl/
i choose
file. (Aside from the cost, this
> would greatly increase the race condition hazards from concurrent psql
> sessions trying to write the file at the same time.)
I think it would be enough to track previous and current database name,
and re-do the history code on change.
depesz
--
Linkedin:
t;
> I don't know what changed in your installation, but it wasn't this.
Any reason why Pg can't parse TZ?
perhaps it should be also listed in
http://www.postgresql.org/docs/current/interactive/functions-formatting.html
doc, that you can't use TZ (and some other patterns too
or reindex - if you *really* need it (are you sure? what makes you
think you need it), then there are ways to do reindex without actually
using "reindex" command, which are mostly transparent for users, but you
should check if you really need to run reindex at all.
Best rega
x27;t use alias on the left side in assignment.
proper query:
update foos as t
set foo_text = '';
this works even if you join another table that has foo_text column, as
update knows which table you're updating.
Best regards,
depesz
--
Linkedin: http://www.linkedin.com/in/depes
Function date_trunc is not IMMUTABLE
> Details:
>
> Please mark function date_trunc as IMMUTABLE for using in index.
it cannot be immutable. please check explanation in here:
http://www.depesz.com/index.php/2010/09/09/why-is-my-index-not-being-used/
search for "immutable&quo
char(x) datatype?
if yes - please read:
http://www.depesz.com/index.php/2010/03/02/charx-vs-varcharx-vs-varchar-vs-text/
Best regards,
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: http://www.depesz.com/
jid/gtalk: dep...@depesz.com / aim:depeszhdl / skype:depesz_hdl / gg:67490
ould not create locale "fr_FR.UTF-8": Success
What is wrong in here?
In shell, I can do:
LC_COLLATE=fr_FR.UTF-8 sort /tmp/french
and it works as expected.
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
On Wed, Mar 02, 2011 at 01:58:02PM +0100, hubert depesz lubaczewski wrote:
> $ select * from test3 order by x;
> ERROR: could not create locale "fr_FR.UTF-8": Success
> What is wrong in here?
never mind. sort looked like ok, but in fact apparently was't, and after
add
On Wed, Mar 02, 2011 at 06:00:45PM +0200, Heikki Linnakangas wrote:
> On 02.03.2011 14:58, hubert depesz lubaczewski wrote:
> >When I try to create french collation, it seems to work, but fails soon:
> >
> >$ CREATE COLLATION french (LOCALE = 'fr_FR.UTF-8'
as a bug.
Second of all - did you read this part of documentation:
http://www.postgresql.org/docs/8.3/interactive/maintenance.html
Best regards,
depesz
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Thu, Apr 07, 2011 at 06:50:16PM +0530, Halli, Savita wrote:
> Hi Depesz
>
> I understand that this is not a bug but I was not aware of any other way to
> get the information so I reported here.
http://www.postgresql.org/
click on "community"
click on "mailing list
-
0/220
(1 row)
$ create database pgdba;
CREATE DATABASE
$ create user postgres with superuser;
CREATE ROLE
$ create user depesz with superuser;
CREATE ROLE
$ create database depesz with owner depesz;
CREATE DATABASE
Afterwards, I exited psql, and simulated power-failure,
5-02 02:00:00+05'::timestamptz;
timestamptz
2011-05-02 02:00:00+05
(1 row)
$ SELECT date_trunc('day', '2011-05-02 02:00:00+05'::timestamptz);
date_trunc
2011-05-02 00:00:00+05
(1 row)
depesz
--
The best thing
ractive/ddl-inherit.html
5.8.1 Caveats
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make chan
ibility with the SQL standard;
>> escape_string_warning has produced warnings about this usage for years. E''
>> strings are the proper way to embed escapes in strings and are unaffected by
>> this change.
Best regards,
depesz
--
The best thing about
ces, and it looks like you're
trying to do it.
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgre
lds for lastname and
firstname, and not put them both in the same column.
In Pg 9.1 you will be able to sort it the way you want using COLLATE
support.
with current situation, you can try to split every string using ", ",
and sort splitted elements separately.
Be
or the end can be written first; OVERLAPS automatically
takes the earlier value of the pair as the start. Each time period is
considered to represent the half-open interval start <= time < end, unless
start and end are equal in which case it represents that single time
instant. This means for
which is bad, because I
explicitly specified the port to be 4329.
before backend crash, \c works normally.
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
at information separately, but I'm not sure
> it's really worth the trouble.
well, I think it's definitely worth the trouble. If I had datbaase
standing at 5432, it would connect to it, and then I could mistakenly
ran commands to wrong database.
this is clearly not a good thing.
depe
On Tue, Sep 06, 2011 at 11:35:43AM -0400, Tom Lane wrote:
> hubert depesz lubaczewski writes:
> > On Mon, Sep 05, 2011 at 02:27:23PM -0400, Tom Lane wrote:
> >> It's not just the port, it's all the connection parameters ---
> >> do_connect relies on the PG
first?
http://www.depesz.com/index.php/2008/11/05/waiting-for-84-suppress_redundant_updates_trigger/
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
--
Sent via pgsq
erating system: OSX 10.6.8
> Description:
>
> CREATE OR REPLACE FUNCTION kill_backend()
> RETURNS VOID
> AS $$
> DROP TABLE if EXISTS foo;
> CREATE TABLE foo AS SELECT * FROM pg_class LIMIT 1;
> $$ LANGUAGE 'SQL';
Cannot replicate:
(depesz@localhos
ating system: Linux
> Description:
>
> SELECT * FROM table1 where col1 in (select col2 from table2)
>
> if col2 exist in table1 and not exist in table2 there will be no error and
> query output all rows from table1;
sure. it is so called "correlated subquery" and
valid, making it mostly useless.
I fail to see how's that a bug. Using functions in check has uses, and
the fact that you don't suit your particular case (or you don't know how
to make them suit your case) is not a bug in Pg.
Best regards,
depesz
--
The best thing about modern
y *variable
datname*". - which is null.
change the select to:
select d.* from pg_database d order by d.datname
and now there is no more problem - because you're no longer using
ambiguous identifier.
Also, check this:
http://www.depesz.com/2009/12/16/waiting-for-8-5-plpgsql-variable-resolu
relation with OID 16503
looks like some missing dependancy.
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
-
Sent via pgsql-bugs mailing list (pgsql-bugs
it also doesn't generate
> any errors so everything looks fine until I try to write to the table. Any
> ideas as to why this wouldn't work or how to make a table with the given
> columns?
most likely you did insert like:
insert into mod_1237 (Collecteddepth) values (...)
i.e. you didn
On Wed, Nov 14, 2012 at 10:00:08AM -0600, Matthew Kuss wrote:
> Depesz -
>
> I'm fairly sure it's not a problem with something I'm doing wrong
> because I've used the same code before. It has to be something wrong
> on the DB side. But just to e
On Tue, Jan 29, 2013 at 06:20:05PM +, kurt.l...@cello.com wrote:
> template1=# copy pg_aggregate to '/tmp/agg.bin' with format binary;
correct syntax:
copy pg_aggregate to '/tmp/agg.bin' with (format 'binary');
Best regards,
depesz
--
The best thing about
x80\x86a');
to_tsvector
-
(1 row)
and for larger example:
$ select to_tsvector('english', E'depesz\xe2\x80\x86whatever');
to_tsvector
---
'depesz':1 'whatev':2
(1 row)
$ select to_tsquery('eng
On Thu, Mar 14, 2013 at 11:56:19PM -0400, Tom Lane wrote:
> hubert depesz lubaczewski writes:
> > $ select to_tsquery('english', E'a\xe2\x80\x86a');
> > ERROR: syntax error in tsquery: "a a"
>
> > the 3-byte utf8 character is SIX-PER-EM SP
ZoneEurope/Berlin 0:53:28 - LMT 1893 Apr
1:00C-Eur CE%sT 1945 May 24 2:00
1:00 SovietZone CE%sT 1946
1:00Germany CE%sT 1980
1:00EU CE%sT
Best regards,
depe
start pg with:
1. cd test/slave; pg_ctl -D . start
or
2. pg_ctl -D /home/test/test/slave start
only when Pg is started with relative path, and restarted with absolute, the
problem shows.
I know that it's probably not a big deal for most of the people, but it
did bite me, so I'm reporting
got exactly same result:
=$ pg_ctl -D q -l logfile start
server starting
=$ cd q
=$ pg_ctl -D $( pwd ) -m fast restart
waiting for server to shut down done
server stopped
server starting
postgres cannot access the server configuration file
"/home/depesz/q/q/postgresql.conf": No s
.
Please provide the command, what you're getting, and why you think it's
a bug.
Best regards,
depesz
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
--
2
(1 row)
I think that the additional row (with stainherit = true) should be deleted.
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
--
Sent via
'::text[]);
Or, perhaps better, with this one:
select unnest('{a,b,c,d,e,f}'::text[]), unnest('{1,2,3,4}'::text[]);
It doesn't show 6 rows (as first array), or 4 (as the other). or 24 (6
* 4). It shows 12, because this is the smallest common multiple of 6 and
4.
depe
d to unpack to join.
you can do:
select * from tablea join tableb on tableb.id = any (tablea.array_column);
depesz
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
83 matches
Mail list logo
