On Thu, Mar 24, 2016 at 5:57 AM, Adrian Klaver
wrote:
> On 03/23/2016 12:02 PM, Moreno Andreo wrote:
>>
>> Il 23/03/2016 19:57, Adrian Klaver ha scritto:
>>>
>>>
>>> Might help to look in:
>>>
>>> Control Panel --> Administrative Tools --> Event Viewer
>>
>>
>> No help there. Nothing strange or po
On Mon, Feb 29, 2016 at 6:31 AM, Stephen Frost wrote:
If we had plenty more bits to allow ANALYZE to be independently
GRANT'able, then maybe, but those are a limited resource.
On Mon, Feb 29, 2016 at 10:35 AM, Joshua D. Drake
wrote:
3. This can already be handled by GRANT:
* psql -U jd -h l
Hi,
Thank you very much. It help us a lot
--
View this message in context:
http://postgresql.nabble.com/Doesn-t-PostgreSQL-clean-data-in-data-file-after-delete-records-from-table-tp5894764p5894960.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql
On 03/23/2016 12:02 PM, Moreno Andreo wrote:
Il 23/03/2016 19:57, Adrian Klaver ha scritto:
Might help to look in:
Control Panel --> Administrative Tools --> Event Viewer
No help there. Nothing strange or pointing to critical resource usage.
The only thing I have left is the generic answer
Il 23/03/2016 19:57, Adrian Klaver ha scritto:
Might help to look in:
Control Panel --> Administrative Tools --> Event Viewer
No help there. Nothing strange or pointing to critical resource usage.
Thanks in advance,
Moreno.
--
Sent via pgsql-general mailing list (pgsql-gene
On 03/23/2016 11:43 AM, Moreno Andreo wrote:
Hello,
a customer of ours has an old PC (CoreDuo, 4 GB RAM, Windows XP)
that's running PostgreSQL. Yesterday PostgreSQL started crashing
suddenly with the following log
2016-03-23 10:40:42 CET LOG: CreateProcess call failed: unrecognized
winsock
Hello,
a customer of ours has an old PC (CoreDuo, 4 GB RAM, Windows XP)
that's running PostgreSQL. Yesterday PostgreSQL started crashing
suddenly with the following log
2016-03-23 10:40:42 CET LOG: CreateProcess call failed: unrecognized
winsock error 10004 (error code 1450)
2016-03-23 1
On Mon, 2016-03-21 at 15:58 +0100, Alexander Farber wrote:
> Thanks for your replies.
>
>
> While I use "\i" regularly I just didn't realize it would be suitable
> here as well :-)
>
\ir migth be a better option for a bundle of scripts, related to main
script (words.sql in your case), not to cwd
On Wed, Mar 23, 2016 at 03:27:45AM -0700, zh1029 wrote:
> Hi,
> we are using PostgreSQL 9.3.6 version and observe data file size is not
> decreased after we deleted records from the table. It looks quite abnormal.
> Is it as PostreSQL designed?
>
> DBTestPostgres=# select count (*) from test_da
Hi,
we are using PostgreSQL 9.3.6 version and observe data file size is not
decreased after we deleted records from the table. It looks quite abnormal.
Is it as PostreSQL designed?
DBTestPostgres=# select count (*) from test_data ;
0
# ls -l
total 788932
.
-rw--- 1 _nokfss
On Wed, Mar 23, 2016 at 9:39 AM, Chris Travers
wrote:
> Use a view with a DO INSTEAD trigger. That will allow you to return the
> tuple properly.
>
> On Tue, Mar 22, 2016 at 7:40 PM, CS DBA
> wrote:
>
>> Hi All;
>>
>> we setup partitioning for a large table but had to back off because the
>> r
Use a view with a DO INSTEAD trigger. That will allow you to return the
tuple properly.
On Tue, Mar 22, 2016 at 7:40 PM, CS DBA wrote:
> Hi All;
>
> we setup partitioning for a large table but had to back off because the
> return status (i.e: "INSERT 0 1") returns "INSERT 0 0" when inserting i
12 matches
Mail list logo
