Hello,
I think adding a force option to dropdb is usefull for many purposes, mainly;
scripting. For example, in a test enviroment, I restore a daily backup of
production databases. The newly created databases are used as templates for
development and also for reading, thus replacing them is com
ave added an option -k, --kill instead of force since killing client
connection does not guarantee -drop force-.
Regards
On Tuesday, January 14, 2014 8:06 PM, Alvaro Herrera
wrote:
salah jubeh wrote:
> For the sake of completeness:
> 1. I think also, I need also to temporary dis
2014年1月17日 0:56, salah jubeh wrote:
>
>>If the user owns objects, that will prevent this from working also. I
>>have the feeling that adding DROP OWNED BY and/or REASSIGNED OWNED BY
>>calls to this utility would be a bit excessive, but who knows.
>
> Please find attach
Hello,
Today, I have noticed that ./configure does not return an error when bison and
flex are missing. Is this intended ?
OS: Ubuntu 13.04
Regards
nks for the quick reply. For curiosity reasons why the differentiation
between tar and git.
Regards
On Tuesday, January 28, 2014 3:18 PM, Heikki Linnakangas
wrote:
On 01/28/2014 04:14 PM, salah jubeh wrote:
> Today, I have noticed that ./configure does not return an error when bison
&g
Hello Heikki,
Thanks for sharing.
Reagrds
On Tuesday, January 28, 2014 3:48 PM, Heikki Linnakangas
wrote:
On 01/28/2014 04:28 PM, salah jubeh wrote:
>> Yes. Bison and flex are not required when building from a source
>> tarball, because the tarball includes the generat
Hello Robert,
>I'm not particularly in favor of implementing this as client-side
>functionality, because then it's only available to people who use that
>particular client. Simon Riggs proposed a server-side option to the
>DROP DATABASE command some time ago, and I think that might be the way
>
| | | | | postgres=CTc/postgres
>hoge database is not dropped yet.
>Is this the bug? or not?
It is a bug, sorry for doubling your work. I have updated the patch.
Regards
On Wednesday, January 29, 2014 8:50 PM, Robert Haas
wrote:
On Wed, Jan
i, Jan 31, 2014 at 9:09 AM, salah jubeh wrote:
>>$ createdb -U postgres hoge
>>$ psql -d hoge -U postgres
>>hoge=# create table test (col text);
>>hoge=# insert into test select repeat(chr(code),1) from
>>generate_series(1,10) code;
>
>>
&g
Hello,
I find default values confusing when a function is overloaded, below is an
example.
CREATE OR REPLACE FUNCTION default_test (a INT DEFAULT 1, b INT DEFAULT 1, C
INT DEFAULT 1) RETURNS INT AS
$$
BEGIN
RETURN a+b+c;
END;
$$
LANGUAGE 'plpgsql';
CREATE OR REPLACE FUNCTION
fits of the way the default parameters are defined; but also,
they are affecting overloading. May be, a warning message when creating a
function like above would be nice.
Regards
On Wednesday, February 26, 2014 7:51 PM, Josh Berkus wrote:
On 02/26/2014 10:15 AM, salah jubeh wrote:
> I
11 matches
Mail list logo
