On Wed, Jun 12, 2013 at 12:19:51PM +0200, Denis de Bernardy wrote:
> … where groups is a crazy column containing an array that needed to be
> joined with another table. In this case, you cannot do your suggested
> solution, which would look like this:
Missed this one.
You don't need to unpack to
On Wed, Jun 12, 2013 at 12:19:51PM +0200, Denis de Bernardy wrote:
> Methinks the behavior should be consistent. It should always do one
> (presumably like in the first statement) or the other (which leads to
> undefined behavior in the first statement).
It is consistent. You just assume it does s
Tested on todays HEAD of 9.3.
Steps to reproduce:
$ create table t1 (i int4);
CREATE TABLE
$ insert into t1 (i) values (1);
INSERT 0 1
$ analyze t1;
ANALYZE
$ select count(*) from pg_statistic where starelid = 't1'::regclass;
count
---
1
(1 row)
$ create table t2 () inherits (t1);
On wto, maj 28, 2013 at 01:36:48 +, bkhamphous...@sopragroup.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8183
> Logged by: khamphousone
> Email address: bkhamphous...@sopragroup.com
> PostgreSQL version: 9.2.3
> Operating system: Linux
On czw, maj 16, 2013 at 05:55:54 -0400, Alvaro Herrera wrote:
> > > only when Pg is started with relative path, and restarted with absolute,
> > > the
> > > problem shows.
> > It has been a nuisance for me too. Possible patch for pg_ctl is in the next
> > CF:
> >
> > http://www.postgresql.org/
hi,
I have 9.3beta1, and strange problem.
Have running slave pg in directory /home/test/test/slave:
=$ pwd
/home/test/test/slave
=$ cat postmaster.pid
16961
/home/test/test/slave
1368736261
5433
/tmp
*
5433001 7241781
=$ ps uxf
USER PID %CPU %MEMVSZ RSS TTY STAT START TI
On pią, maj 10, 2013 at 10:34:02 +0200, Karsten Düsterloh wrote:
> Under Pg 8.3, we used the timestamp
> 0001-01-01 00:00:00+01
> as an easy-to-remember marker for 'dunno, but predates any usual
> business dates' for fields of type timestamp with time zone.
Why didn't you use "-infinity" for thi
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
hi
it was tested on 9.1 and 9.3. Interestingly - it worked without error in
8.2.
$ 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 SPACE (based on info from
http://www.fileformat.info/info/unicode/char/2006/index.htm)
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 modern society is how easy it is
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 entertain you I did as you requested:
>
> RigMinder_N
On Tue, Nov 13, 2012 at 04:59:53PM +, m...@rigminder.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7657
> Logged by: Matt
> Email address: m...@rigminder.com
> PostgreSQL version: 9.1.4
> Operating system: Windows Server Standard SP2
> D
tested on:
1. 9.1.3
2. 9.3devel (yesterdays head in git)
steps to reproduce:
$ create table z (i int4);
CREATE TABLE
$ create unique index q on z (i);
CREATE INDEX
$ alter table z add primary key using index q;
ALTER TABLE
$ alter table z alter column i type int8;
ERROR: could not open relati
On Fri, Jul 27, 2012 at 02:56:18PM +, bo...@folgmann.de wrote:
> This is an really interesting one!
> I've trimmed down the problem so you can simply reproduce it by copy &
> paste:
> The only difference of the two functions is that the first one uses a
> variable with the same name of a column
On Wed, Apr 25, 2012 at 10:33:10AM +, atrig...@ccs.neu.edu wrote:
> Seeing as Postgres does not allow sub-queries in CHECK constraints yet, it
> doesn't make any sense to me for it to allow function calls, since functions
> can perform queries. Additionally, if a function is called from a check
On Mon, Feb 27, 2012 at 11:39:55AM +, anisim...@gmail.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6490
> Logged by: Timofey Anisimov
> Email address: anisim...@gmail.com
> PostgreSQL version: 9.1.2
> Operating system: Linux
> Descript
On Wed, Jan 04, 2012 at 07:17:17PM +, pram...@cleverelephant.ca wrote:
> The following bug has been logged on the website:
>
> Bug reference: 6379
> Logged by: Paul Ramsey
> Email address: pram...@cleverelephant.ca
> PostgreSQL version: 9.1.2
> Operating system: OSX 10.6.8
On Sun, Dec 04, 2011 at 12:54:25PM +, dmigow...@ikoffice.de wrote:
> It seems that an update to a row in a table always removes the element from
> an index and adds it again. Wouldn't it be faster to check for equality of
> the index parameters in the OLD and NEW record first?
http://www.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
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 PGconn object to remember those, and in this
> case there no longer is a PGconn object.
>
> We could have psql keep that information separately, but
hi,
pg version: 9.0.5 - head from 9.0 branch in git.
ran psql with specyfying port:
psql -p 4329 -U postgres -d some_database
then I run query which breaks backend:
=# select * from categories limit 1;
The connection to the server was lost. Attempting reset: Failed.
!>
When I'll try to re-issue
On Wed, Jul 20, 2011 at 06:09:48AM +, Ludek Bouska wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6124
> Logged by: Ludek Bouska
> Email address: lu...@bouska.info
> PostgreSQL version: 8.3.7
> Operating system: FreeBSD 7.2-RELEASE-p3
> Descriptio
On Mon, Jun 13, 2011 at 09:52:06PM +, Mike Hepworth wrote:
> I execute the following sql statment:
>
> select * from (values('HALL, ANDY'),('HALLBERG, FRANK'),('HALLDEN,
> DOUGLAS'),('HALL, DOUGLAS') ) x ORDER BY 1;
>
> and get the following results
>
> HALL, ANDY
> HALLBERG, FRANK
> HALLDEN
On Sun, May 29, 2011 at 11:16:30AM +, Emanuel wrote:
> make and make installs work well. To compile correctly I must hardcode the
> libdir. I happens with several contribs.
did you actually do make and make install *in* contrib directory?
one shouldn't load sql files from the sources, and it
On Tue, May 10, 2011 at 06:20:23PM +0200, Martin Pitt wrote:
> Since HISTORY does not mention this, is that an explicit decision to
> finally deprecate the old \' syntax (which would be great, as it makes
> this thing a lot more robust and deterministic, but it might be worth
> mentioning it in HIS
On Tue, May 03, 2011 at 10:12:53PM +, David carlos Manuelda wrote:
> Is it a duplicate of what is in TODO and I understood it bad, or is this a
> new issue?
well, possibly neither. It's limitation well known, and described in
docs:
http://www.postgresql.org/docs/9.0/interactive/ddl-inherit.htm
On Sun, May 01, 2011 at 06:48:57PM +, Marek Nos wrote:
>
> The following bug has been logged online:
>
> Bug reference: 6001
> Logged by: Marek Nos
> Email address: marek@centrum.cz
> PostgreSQL version: 9.0
> Operating system: Windows 7
> Description:date_trunc
hi
got new 9.1, straight from git.
compiled, installed.
did initdb, and then set config values using this script:
perl -pi -e '
s/\A \s* (?: [#] \s* )? listen_addresses \s* = \s*.*/listen_addresses =
\047*\047/x;
s/\A \s* (?: [#] \s* )? log_destination \s* = \s*.*/log_destination =
\047stderr
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 lists"
pick one, subscribe, and a
On Thu, Apr 07, 2011 at 07:38:49AM +, Savita wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5967
> Logged by: Savita
> Email address: savita.ha...@ca.com
> PostgreSQL version: 8.3.5
> Operating system: Linux
> Description:Db maintainace
>
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'
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
hi
i'm trying to test collation per column on newest pg head, but I can't
seem to get it working.
my normal locale is en_US.UTF-8, but in database, for test purposes I
used pl_PL.UTF-8.
Which works.
When I try to create french collation, it seems to work, but fails soon:
$ CREATE COLLATION fren
On Thu, Feb 10, 2011 at 11:02:40AM +, Savita wrote:
> When I ran query to get the ids which ends with B1
> select id from table where id like '%B1'
> does not return me any rows. Should it be not returning row with id AB1? Is
> there known issue?
is this by any chance char(x) datatype?
if yes
On Thu, Jan 27, 2011 at 11:02:46AM +, Oleg wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5852
> Logged by: Oleg
> Email address: sero...@gmail.com
> PostgreSQL version: 8.3
> Operating system: CentOS
> Description:Function date_trunc is n
On Wed, Jan 26, 2011 at 06:05:40PM +, Joshua Farray wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5850
> Logged by: Joshua Farray
> Email address: far...@gmail.com
> PostgreSQL version: 9.0.2
> Operating system: Win7 x64
> Description:UPD
On Sun, Nov 28, 2010 at 07:25:52AM +, Bala Murugan wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5774
> Logged by: Bala Murugan
> Email address: b...@a-cti.com
> PostgreSQL version: 8.3.7
> Operating system: openSUSE 10.3 (X86-64) - Kernel \r (\l
On Sun, Oct 17, 2010 at 11:10:09AM -0400, Tom Lane wrote:
> "Alexander Loechel" writes:
> > After an update on my ubuntu system of postgres 8.4.4 to 8.4.5 the
> > to_timestamp methode produces different results.
>
> > in a CREAT View statement I have following methode call:
> > to_timestamp(dbtim
On Thu, Aug 12, 2010 at 06:33:13PM -0400, Tom Lane wrote:
> "David E. Wheeler" writes:
> > I have this in my .psqlrc:
> > \set HISTFILE ~/.psql_history- :DBNAME
> > This is great, except when I change databases in a session:
>
> > % psql foo
> > foo % \c bar
> > You are now connec
Hi,
I tried to use exclusion for time ranges, with this table and data:
CREATE TABLE test (
from_ts TIMESTAMPTZ,
to_ts TIMESTAMPTZ,
CHECK ( from_ts < to_ts ),
CONSTRAINT overlapping_times EXCLUDE USING GIST (
box(
point( extract(epoch FROM from_ts at time zone
Version - 8.5devel.
Why this doesn't work:
# SELECT 1 = ANY( ( SELECT '{1,2}'::int4[]) );
ERROR: operator does not exist: integer = integer[]
LINE 1: SELECT 1 = ANY( ( SELECT '{1,2}'::int4[]) );
^
HINT: No operator matches the given name and argument type(s). You might need
to
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_hdl / gg:6749007
-
On Fri, Aug 21, 2009 at 04:26:11PM +, Sebastien Lardiere wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5004
> Logged by: Sebastien Lardiere
> Email address: slardi...@hi-media.com
> PostgreSQL version: 8.3.7
> Operating system: Debian Etch
> Desc
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/gtalk: dep...@depesz.c
While testing deferred unique constraints I found this:
# CREATE TABLE test (
i INT4 PRIMARY KEY
);
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "test_pkey" for
table "test"
CREATE TABLE
# set constraints test_pkey deferred;
ERROR: constraint "test_pkey" does not exist
Th
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
Hi,
I tested it on 8.3.7 and on 8.4, but it doesn't seem to be version
bound.
steps to reproduce:
# create table sold_products (items int4, product_id int4);
# create table products (id int4, codename text);
# select sp.count, p.codename from sold_products sp join products p on
sp.product_id = p
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
--
Linkedin: http://w
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
--
Linkedin: http://w
I was under impression that select distinct on (xx) ...
will fail if xx doesn't match the left most part of order by. i.e. it
requires order by xx, while allowing order by xx, something, else.
But it seems you can run the query with no order by clause at all.
is it intentional?
# select distinct
On Mon, Apr 20, 2009 at 11:08:56AM -0700, Scott Wells wrote:
> I am trying to script a pg_dumpall command set to use in a crontab
> entry.
> The problem I am finding is that the command pg_dumpall seems to be
> ignoring the -W input.
not sure what you mean by -W input. -W is a switch to force too
hi
just tried to build newest head. while building docs i got:
+ cd ../doc/src
+ make -j 3 postgres.tar
make -C sgml html JADEFLAGS='-V html-manifest'
make[1]: Wejście do katalogu `/home/pgdba/src/pgsql/doc/src/sgml'
test -s HTML.index || LC_ALL=C "/usr/bin/perl" /usr/bin/collateindex.pl -f -g
-o
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.com/
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)||''::TEXT'' ||
Best regards,
depesz
--
Linkedin: http://www.linkedin.com/in/depesz / blog: htt
On Wed, Nov 12, 2008 at 06:45:27PM +, chris wood wrote:
> I apologize in advance for not testing on 8.3.5, but that would be very
> difficult for me.
> I e-mailed this same problem from [EMAIL PROTECTED] and it got
> blocked
http://www.postgresql.org/docs/current/interactive/release-8-3-2.ht
On Mon, Oct 27, 2008 at 05:08:35PM +0300, Oleg Serov wrote:
> I can't get hstore value by key. i have very interesting error
the problem is that -> has very low priority, but you work with it
anyway:
# select tconvert('a', 'b')->'a' is null;
ERROR: operator does not exist: hstore -> boolean
LINE
there is a typo on postgresql ftp server:
=> lftp ftp.postgresql.org
lftp ftp.postgresql.org:~> cd pub
cd ok, cwd=/pub
lftp ftp.postgresql.org:/pub> ls -l
-rw-rw-r--1 258 70 1719 Dec 10 2007 README
-rw-rw-r--1 258 70 1552 Feb 09 2008 README.dist-split
drwxrw
On Sat, Sep 27, 2008 at 12:46:31AM +, Anatoli Lau wrote:
> select regexp_matches('/a/b[534]', E'(.*)\[([0-9]*)\]');
> always gives the error but
> select regexp_matches('/a/b{534}', E'(.*)\{([0-9]*)\}');
> works good, the problems comes up only when '[' used
it would be good to show what kind
On Wed, Sep 17, 2008 at 02:53:51PM +, vasile wrote:
> I have this 2 similar queries.
>
> Why the 1st query is returning 1000+ rows and the 2nd one no rows ?
> The col1 is not empty in both tables.
there is no bug.
check this:
http://www.depesz.com/index.php/2008/08/13/nulls-vs-not-in/
On Tue, Jul 22, 2008 at 09:33:31AM -0400, Alexandre Payment wrote:
> I was just hoping that basic commands like \d will be backward
> compatible. Maybe I'm just too optimist.
It would be cool, and I had read someplace about some works toward it, but
it doesn't work that way now.
But. Since you're
On Thu, Jun 05, 2008 at 06:15:29PM +, Lawrence Cohan wrote:
> Following queries run FOREVER in PG if an index exists on the "id" column
> which is a integer - serial and PKey on the table.
> SELECT id FROM orders WHERE merchant_id = xx ORDER BY id DESC LIMIT 31
> -- or 30, 29, 28, 27, 26,
On Wed, Jun 04, 2008 at 01:58:19PM -0700, Lon Varscsak wrote:
> Wow, I want it to violate the spec so I can get my rows back! :)
> I understand the problem and why it did what it did now though.
you might find this post also helpful (for future):
http://www.depesz.com/index.php/2007/07/27/update-
On Wed, Jun 04, 2008 at 06:46:42PM +, Lon Varscsak wrote:
> delete from customer_transactions_detail where transaction_id in (select
> transaction_id from test);
> The transaction_id column does NOT exist in the temporary table named
> 'test'). I would think this would just result in an error,
apparently revoking update rights on referencing table blocks deletes on master
table:
(user test, database test, user test is not superuser)
> create table a (id serial primary key, x text);
NOTICE: CREATE TABLE will create implicit sequence "a_id_seq" for serial
column "a.id"
NOTICE: CREATE
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 requires a
hi
if i create sequence m and then want to change it's owner to some other
account i have to issue:
alter table owner to ...;
why can't it be: alter sequence?
example:
# create sequence x;
CREATE SEQUENCE
# \d
List of relations
Schema | Name | Type | Owner
+--+--
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 dla ciebie (i moje CV)
1. postgresql 8.2.4
2. system is 8-way xeon, 64bit with 32gram.
3. autovacuum is (and was) turned off in configuration.
4. today in peak hours autovacuum started. no mention of it in logs. it
just showed. started to vacuum the largest table in main database, and
brought the website down due to enor
On Mon, Sep 10, 2007 at 11:17:21AM -0400, Tom Lane wrote:
> > ok, but i belive it should either dont allow admin to do so, or, if it
> > does allow, it should behave more consistently.
> There are few "training wheels" for superuser mode. Try something like
> "delete from pg_proc" if you are looki
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
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
ERROR: p
steps to reproduce:
session1: connect using user1 to database1.
session2: connect using user2 to database2.
session1: create table x ( y int);
session2: begin;
session1: create index concurrently q on x(y);
it hangs.
session2: rollback/commit;
session1: finishes.
i dont really see why this would b
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
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.
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
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
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
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
pping all privileges "by hand" might be
major pain when dealing with > 100 tables with several hundreds of
views, procedures and so on.
depesz
--
hubert depesz lubaczewski http://www.depesz.pl/
> wynajmę mieszkanie - 60 metrów, 3 pokoje, piastów - od
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/
-
ba"
LOG: fast shutdown request
LOG: shutting down
LOG: database system is shut down
interesting part is that it wrote only once about authentication for
pgdba ...
is it a bug or compilation failure?
depesz
--
hubert depesz lubaczewski http://www.
--
hubert depesz lubaczewski http://www.depesz.pl/
... vows are spoken to be broken ... [enjoy the silence]
... words are meaningless and forgettable ... [de
82 matches
Mail list logo
